I think that a basic answer is that this would be either an extension (as done with OpenSocial for the same reasons) or a separate service (give the token, get the stable identifier for the user, if they want to share it with you). However, you may also want to look at the hybrid OpenID-OAuth flow that Breno and Eric are working on over on the OpenID mailing lists.
Joe Bowman wrote: > I'm working on a site where I'd like to see if I can use oauth to > allow logins from users of Google, Yahoo, and Myspace. With OpenID, > you get a unique hash for the user that youu store locally to refer > against to identify return visitors. Does oauth have something like > this? I've been reading through documentation and tutorials, and I'm a > bit confused if something like that is part of the protocol. > > What I'm trying to do is user Joe chooses to log in using oauth to my > site. Once the oauth provider authenticates Joe, my server is given > some unique identifier for Joe. I can then store this identifier, plus > site specific profile information I request from him. The next time > Joe logs in, I recognize based off of that unique identifier he's > already a "member" of my site, and use the stored profile information > to enhance his experience. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
