OAuth2 is really just a collection of suggestions. Here's some examples:
* What field should the token be passed back as?
* What are the token + auth URLs?
* Should there be a separate profile URL, or is user data passed back with the token?
* What field is the email address passed back as? The user's name?
* Are refresh tokens used? How?
These are just things I literally ran into today. There's hundreds more things like this.And on top of that, pretty much every single OAuth provider requires custom code: http://passportjs.org/
* Do access token expire and need to be refreshed at all?
* Are scopes used?
* Appropriate header values?
* Can redirect URI be overrided in auth request (my personal favorite)?
* Are scopes used? => https://tools.ietf.org/html/rfc6749#section-3.3
* Appropriate header values? => https://tools.ietf.org/html/rfc6749#section-7 as well as https://tools.ietf.org/html/rfc6750
* Can redirect URI be overrided in auth request (my personal favorite)? Sth. like https://tools.ietf.org/html/rfc6749#section-10.6 ?
most of them did, but there are quite some gaps.
then you extensions and shit to complicate matter further: http://hueniverse.com/2012/07/30/on-leaving-oauth/
I like OpenID efforts to making a OAuth 2.0 subset that works and is authoritative, but to be honest implementing OAuth dialect isn't that much of an issue.
now, having a single consistent user id across services beyond their email, that's an interesting problem to solve.
but for everything OAuth one can find out libraries in many languages.
> * What field should the token be passed back as?
It's passed in the Authorization header.
> * Should there be a separate profile URL, or is user data passed back with the token?
This is outside the scope of OAuth.
> * What field is the email address passed back as? The user's name?
"email address"? "user's name"? These are not concepts built into OAuth…
> * Are refresh tokens used? How?
In a grant_type=refresh request. It's in the spec.