Ok filed a feature request: http://code.google.com/p/googleappengine/issues/detail?id=3280
-g. On May 29, 1:51 am, Robert Kluin <[email protected]> wrote: > Let us know if you make a feature request so we can star it. > > I also notice get_current_user() seems to have two very different > behaviors for OAuth vs Google accounts. The Google accounts returns > None while the OAuth version raises an exception if the user is not > logged in. > > Robert > > On Fri, May 28, 2010 at 3:18 PM, George Moschovitis > > > > <[email protected]> wrote: > >> What about using "get_current_user()"? > > > yeah I meant get_current_user()... > > my problem is that there are two versions of the method: > > > google.appengine.api.oauth.get_current_user() > > google.appengine.api.users.get_current_user() > > > one works with OAuth and one with sign-in (or am I wrong?). > > > I would like google.appengine.api.users.get_current_user() to work > > with OAuth authenticated users too, ie a unified authentication > > mechanism. > > > -g. > > > -- > >http://www.appenginejs.org > > > -- > > 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 > > athttp://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.
