I've got a full OAuth 2.0 implementation about halfway down my list of business priorities. It's not just a case of implementing an extra authorizer: validating an existing token is the easy part and the OAuth spec is silent about the format of tokens - they are opaque.
You will have to decide how you want to implement the rest of the OAuth flow, and how your users will retrieve a token in the first place, as well as what that token looks like. You will need to decide whether you want a blanket access policy, or if you are going to define multiple scopes for authorization, and how you are going to provision client secrets to other developers. If there are no other developers, do not use OAuth.
-- Bob
--
An infinite number of mathematicians walk into a bar. The first one orders a beer. The second orders half a beer. The third, a quarter of a beer. The bartender says "You're all idiots", and pours two beers.