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

Would like email (at least) to be retrieved from federated identity providers #376

Closed
ceich opened this issue Feb 28, 2018 · 3 comments
Closed
Labels
Auth Related to Auth components/category feature-request Request a new feature

Comments

@ceich
Copy link
Contributor

ceich commented Feb 28, 2018

Feature Request

Current behavior: when the user authenticates with Facebook, even though the requested scope includes email, the /me request made by withFacebook defaults the params, which returns only name and id fields. The resulting user object has only those attributes.

I would like to use federated logins to infer my user's identity, and need a stable user id. Lacking any imagination, I would like to use the user's email address. (The app supports all three federated providers, and choosing a different provider results in a different identity pool user id, whereas the email is the same in each provider.)

@ceich
Copy link
Contributor Author

ceich commented Feb 28, 2018

After further thinking I believe I need to use the Federated feature of User Pool itself, which seems to imply hosted login UI.

If this is true, aws-amplify would be out of the picture, at least as far as my needs go.

@manueliglesias manueliglesias added investigating This issue is being investigated Auth Related to Auth components/category labels Mar 1, 2018
@mlabieniec mlabieniec added feature-request Request a new feature and removed investigating This issue is being investigated labels Apr 13, 2018
@mlabieniec mlabieniec added this to the [email protected] milestone Apr 13, 2018
@powerful23
Copy link
Contributor

Closing this issue.

@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Auth Related to Auth components/category feature-request Request a new feature
Projects
None yet
Development

No branches or pull requests

6 participants