Hi warren, There is some discussion about this on the Accounts API group:
http://groups.google.com/group/Google-Accounts-API/web/api-feature-requests I think what you are looking for, if I understand you correctly, is an API that allows you to authenticate a user using their Google Account. Such an API would work similarly to AuthSub in that you can redirect the user to a Google login screen and then Google's servers would redirect them back to your website after authenticating. This is fundamentally different from AuthSub, though, since you're not trying to have your website be granted access to a particular resource, but you do want some form of user registration. I agree this would be a useful service to have, but it would probably need some more discussion on the Accounts API group. Cheers, -Jeff On Aug 27, 5:30 pm, warren <[EMAIL PROTECTED]> wrote: > I'm creating a web application and have a pretty simple question about > the Data API. Essentially, after I get a session token, is there > anyway to get a "unique identifier" of any sort (gmail account name, > id number, UUID, etc) that I can use in my application to store > relational data against this user? > > For example, here's the application flow: > > 1. A user comes to my site. > 2. My site doesn't recognize the user and doesn't have a session token > for them, so it redirects them > tohttps://www.google.com/accounts/AuthSubRequest > with scope/next/session set. > 3. The user logs in to their Google Account and clicks "Grant Access". > 4. The user is returned to my site with a ?token=SOMETHING > 5. My site sees the token and makes a request to AuthSubSessionToken > and gets a session token. > > Now the problem is after step 5, I have a session token for this user, > but I have no idea who this session token is for, or if I have any > previous session tokens I should invalidate for this user, or if I > have any data tied to this user already. > > It seems like there should be some sort of API call I can now make > with this session token that would return at the very least some sort > of unique identifier for this user that's tied to the Google Account > they logged in with. Ideally, it would also return a First/Last name > and even a GMail address. This way, I can have a table that stores > unique_google_id and last_session_token.... so after my step 5, I can > then make an additional API call, request a unique_google_id for the > token, check in my data table to see see if the unique_google_id > already has a last_session_token, and if so, invalidate it through > another API call. Furthermore, I can store relational data against > the unique_google_id in my application. > > It seems like this is a very basic functionality that should already > exist, yet I can't find anything even close... did I just overlook > something? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Data API" 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/google-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
