Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

endpoints.get_current_user() does not support 3rd-party auth #53

Open
lookuptable opened this issue Mar 6, 2017 · 4 comments
Open

endpoints.get_current_user() does not support 3rd-party auth #53

lookuptable opened this issue Mar 6, 2017 · 4 comments
Assignees

Comments

@lookuptable
Copy link
Contributor

Currently the get_current_user() method returns a user object only if the user is created from a Google ID token or an opaque OAuth token. We should fix it so that it works for users from a 3rd-party auth provide.

@lookuptable lookuptable self-assigned this Mar 6, 2017
@gianni-di-noia
Copy link

seems related to #32

@Al77056
Copy link

Al77056 commented May 15, 2017

This is fixed now with version 2.0.5

@gianni-di-noia
Copy link

@Al77056 No, with the 2.0.5 endpoints.get_current_user() returns the google user, the same obj of google.appengine.api.users.get_current_user(), which have nothing to do with the 3rd-party user obj (firebase in my case).

@tangiel
Copy link
Contributor

tangiel commented May 16, 2017

@presveva it's not meant to return a third party SDK object, rather user info decoded from the JWT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants