I did a couple quick tests this evening (in Python). I wrote a couple super simple handlers to walk me through the (three-legged) OAuth setup, then stored the token in the datastore.
One the provider side I wrote a simple utility function, get_user that return users.get_current_user() if it returned a value, if not it tried oauth.get_current_user(), and finally returned None otherwise. It worked correctly. I have not tried this on an OpenID App yet. Robert On Fri, Apr 8, 2011 at 02:47, Jan Z/ Hapara <[email protected]> wrote: > Yesh - it's close, but as I think you pointed out on another thread, not the > same as api.users - which means kludgy code. > > It would really make sense to merge users and oauth, they really are the > same thing from the service consumer standpoint. I *might* want to know > which was used, but 90% of the time, it doesn't matter. > > The impact here is needing to change the existing app, potentially in > unpredictable ways. > > J > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
