That's an interesting scenario. Unfortunately, I don't see a great way to verify which profile the token is good for. Querying the profile/default feed doesn't return any information about the profile's name or ID.
The fix would involve changing the <atom:title> in the profile/ default feed to display the profile's ID/name rather than 'Profile feed': <title type="text">Profile Feed</title> to <title type="text">123456879</title> OR <title type="text">Jen's Healthy Profile</title> Even better would be to make the profile/list feed available to AuthSub (it's currently only accessible by ClientLogin). I agree this is a definite road block. Feel free to open an issue: http://code.google.com/p/gdata-issues/issues/list Thanks, Eric On Oct 2, 5:35 am, th55 <[EMAIL PROTECTED]> wrote: > Our application allows the user to select a family member to be in > scope via a drop down list box. All operations, including requesting > a long life authorization token for that family member from Google > Health, take place with that family member in play. When the user > gets to the Google Health generated "link to my accounts" page during > the linking process, the user can select any of the radio buttons on > the page that select a profile. However, the user could make a > mistake and select a profile that does not agree with the family > member in scope in our application. When we get the authorization > token back from Google, we have no way to verify that the user > selected the proper profile from the linking page. When we store the > token in the database for the family member in play, and then transfer > data to Google Health, the data gets put in the wrong profile. What > we need is to get the token back with qualifying information as to > what profile it applies to. Then, we can check at our end to make > sure the token retrieved actually applies to the family member in > scope. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Health Developers" 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/googlehealthdevelopers?hl=en -~----------~----~----~----~------~----~------~--~---
