No one can help on this? In looking more closely through the docs, it appears that the answer to my first question is yes; the shared uid restriction applies when a third party app wants to manipulate the authenticators credentials directly.
As for the second and third questions, I found this: http://blog.notdot.net/2010/05/Authenticating-against-App-Engine-from-an-Android-app This seems close to what I want, but I'd rather not be tied to GAE. Does anyone know if it is possible to accomplish the same thing (trade in a Google auth token for a server specific login cookie) via generic OpenId? Thanks, Jay On Oct 17, 7:22 am, Jay <[email protected]> wrote: > Several related questions about the account infrastructure: > > Can a third party app use the account API to request a token for and > login to a Google service using the stored credentials? Examples I > have found seem to suggest yes, though I have also read several places > that the account back end and requesting app must share a uid and > signature. > > If I run a server that accepts GoogleOpenID, can I use the account > API and stored credentials to access it transparently (or with a one > time "allow this?" dialog)? > > If it possible to implement a "virtual" account type, one that is > logically different from a Google account (for sync, etc) but that > uses the credentials for an extant Google account? > > Thanks, > Jay -- You received this message because you are subscribed to the Google Groups "Android 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/android-developers?hl=en
