-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
oauth with Digits #2280
Comments
We could definitely add digit as an auth provider |
I have cloud Code functions that handle that, I can provide it once I'm Am Donnerstag, 14. Juli 2016 schrieb Florent Vilmart :
|
Hi @hasso92, @flovilmart - we can use the same code line of the Twitter provider but change only the provider name to digits. In this way developers will be able to provide 2 authentication login , with digits or with Twitter... What do you think ? |
@ranhsd I was thinking about that actually: https://github.com/ParsePlatform/parse-server/blob/master/src/authDataManager/index.js#L9 here add |
@flovilmart - great solution .. I will test it and do a pull request (unless you already did it ;) ) |
go for it, test it :) |
Closing as it's been merged |
Hi ,
twitter Digits provide password-free login for mobile apps. One of the coolest feature of parse-server is to allow users to login with 3rd party providers like: twitter, facebook, instegram etc.
I just wanted to inform you that it is possible to use twitter oauth provider also with Digits.
In order to test it please do the following:
The code above do the following:
The digit session also return the user phone number so you can also store the user phone number in the DB.
This way you can allow your users to login with their phone numbers only (password-free)
BTW, if you have multiple apps and you want to provide one login so user will not need to fill in his/her profile each time they signed up you can use AWS Cognito for that. I tried it and it works great with Parse Server.
More details about it can be found here: http://docs.aws.amazon.com/cognito/latest/developerguide/twitter.html
The text was updated successfully, but these errors were encountered: