This question is locked. New answers and comments are not allowed.
Hello,
I'm working on an app where users have to "find" each other to share TBS data, presumably by entering the target user's email address, since that is unique. I would really like to use the Google, Twitter, LiveID and Facebook login functionality that TBS offers, exclusively. I don't want to build my own authentication or ask users to create yet another account.
My first attempt at using the OAuth stuff worked nicely, but I found that logging in with my Windows LiveID account resulted in a TBS user record being added without an email address or username. That's useless in my application. The Display Name is certainly not unique. So:
1) Is there a way to restrict OAuth registration to users who have configured their social accounts to provide email access? As the doc says "If the provided token has scope for email then the email address provided in the profile will be stored in the Email field of the user." If that scope is missing, can I ask TBS to reject the registration in the cloud code somehow?
2) Or, is there a way to supplement the OAuth registration with an Email address during registration? The reason I ask, I edited my Windows LiveID account, and don't even see any way to specify or allow "scope for email".
What would you do?
Thank you,
Kelly
I'm working on an app where users have to "find" each other to share TBS data, presumably by entering the target user's email address, since that is unique. I would really like to use the Google, Twitter, LiveID and Facebook login functionality that TBS offers, exclusively. I don't want to build my own authentication or ask users to create yet another account.
My first attempt at using the OAuth stuff worked nicely, but I found that logging in with my Windows LiveID account resulted in a TBS user record being added without an email address or username. That's useless in my application. The Display Name is certainly not unique. So:
1) Is there a way to restrict OAuth registration to users who have configured their social accounts to provide email access? As the doc says "If the provided token has scope for email then the email address provided in the profile will be stored in the Email field of the user." If that scope is missing, can I ask TBS to reject the registration in the cloud code somehow?
2) Or, is there a way to supplement the OAuth registration with an Email address during registration? The reason I ask, I edited my Windows LiveID account, and don't even see any way to specify or allow "scope for email".
What would you do?
Thank you,
Kelly