I have a client I've developed an app-engine app for, but for reasons to silly to mention here, they'd like to move to a hosted server model. I've developed my own implementation of all the Google services my code relies on (like Memcache and TaskQueue etc.) however, I'm having a bit of a hard time with the UserService implementation. In particular, it seems I need to use the OpenID protocol to keep on allowing users to login to the system with their GMail accounts. The documentation for Googles OpenID implementation indicate that the userId is dependent on the relying parties credentials (which totally makes sense), this would mean that when our application is hosted off the App-Engine, we're going to get different userId values for users that have already authenticated to our system. This makes data migration a bit touchy.
The App-Engine docs seemed to indicate that the supplied userId was the same for all apps requesting user authentication. Is there a way I can use the same mechanism for user login when my app is running on a different server? My main concern revolves around the fact that we use the Google supplied userId as a unique identifier for users rather than their email address, since the App-Engine documentation indicated that users can change their email address, and the only "stable" identifier was the userId. Has anyone migrated off the App-Engine (for whatever reason) and been able to maintain the user authentication? If not, does anyone at Google have any suggestions as to how to migrate the data such that I can recognize return users and load their historical data? Thanks in advance -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
