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
I am sorry if this is the wrong place, not sure where to post a feature request.
Details:
Right now it's not possible (as far as I know) to use different OAuth methods for the same user account.
I login with Facebook, a user is created. I login with Twitter, another user is created and so on.
Ideally it shouldn't matter what OAuth method (LinkedIn, Facebook, Twitter, ...) a user uses, they should all point to the same account. Amazon already does this with the Cognito service that returns the same unique ID independent of the OAuth provider.
I am wondering if something similar could be implemented with parse server, maybe even by leveraging AWS Cognito.
The text was updated successfully, but these errors were encountered:
Once you have signed up or logged in with say a twitter account, submit a PUT request with FB authData and a valid user session token to link Facebook to the same Twitter based account.
I haven't tried it yet but if you use multiple oAuth in your app you should give it a try and see if it works as intended.
I am sorry if this is the wrong place, not sure where to post a feature request.
Details:
Right now it's not possible (as far as I know) to use different OAuth methods for the same user account.
I login with Facebook, a user is created. I login with Twitter, another user is created and so on.
Ideally it shouldn't matter what OAuth method (LinkedIn, Facebook, Twitter, ...) a user uses, they should all point to the same account. Amazon already does this with the Cognito service that returns the same unique ID independent of the OAuth provider.
I am wondering if something similar could be implemented with parse server, maybe even by leveraging AWS Cognito.
The text was updated successfully, but these errors were encountered: