You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
Feature Request
Current behavior: when the user authenticates with Facebook, even though the requested scope includes email, the
/me
request made bywithFacebook
defaults the params, which returns onlyname
andid
fields. The resultinguser
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.)
The text was updated successfully, but these errors were encountered: