In regard to OAuth 2.0 authentication providers, the 'scope' of the request obtaining the token for the user will require from the provider's API a specific information for the user. You can refer to our 'Friends' sample app to see the required configuration
In order to receive the email of the user, for the different social authentication providers the "scope" must be set with the following values:
- for LiveID set the scope to:
- for Google set the scope to:
- for Facebook set the scope to:
These examples are for hybrid app, but the same configuration is applied for the requests to the OAuth providers' APIs constructed with other programming languages.
In regard to OAuth1a providers (e.g. Twitter) the email of the user is not provided by the authentication authority. The client app has to obtain explicitly the email address by asking the users to enter it manually.
Note that the current logic of the backend does not allow a user to be created, if an account with the same email already exists. In the case of social authentication, a user already authenticated with Google will not be able to switch using his/hers LiveId account that uses the same email address). You may implement a 'linking' logic in the client app to handle such cases, if applicable.
Please, let us know if this is helpful for you.
Everlive is now Telerik Backend Services
, and is part of the Telerik Platform
. For more information on the new name, and to learn more about the Platform, register for the free online keynote and webinar
on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT)