OpenID Connect (http://openidconnect.com/) is an alternative version of OpenID build on OAuth. It considers this use case as well and returns a user identifier which can be used to get username etc. in a standardized manner via OAuth.
Regards, Lukas 2010/5/20 Leah Culver <[email protected]> > Many APIs have an endpoint solely for getting information about the > authenticated user. I think Twitter's is account/verify_credentials... > > Leah > > > On May 16, 2010, at 5:36 PM, "Richer, Justin P." <[email protected]> > wrote: > > Nothing exists for this specifically in OAuth, partially because not all >> APIs have a notion of a "username". However, I think that it makes sense to >> have a notion of per-instance metadata attached to a token. For example, if >> a user has two instances of a thick client, both of those will have tokens >> in the server end, but since they'll both have the same client ID there's no >> way to tell them apart. Username could be one of these kinds of per-instance >> meta ields. I floated this idea on the list a while back and never got >> traction on it. >> >> -- justin >> > -- http://lukasrosenstock.net/ -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
