Progress will discontinue Telerik Platform on May 10th, 2018. Learn more

Enabling a Social Login Provider

Enabling a Social Login Provider

Before you can start implementing social login with a particular provider, you need to tell Telerik Platform to enable it. Otherwise your backend will return an error even if your code is properly implemented.

Enabling Facebook

Facebook only requires selecting a check box. You do not need to enter additional data.

  1. Go to Users > Authentication.
  2. Under Enable authentication providers, select the Facebook check box.
  3. Click Save.

Enabling Google

Enabling Google Sign-In comes with the option to enter a Google app Client ID. When you provide it, Telerik Platform will verify that Google ID tokens actually match the Client ID. This prevents malicious apps from accessing your app's data using ID tokens issued to them.

You can enter multiple Client IDs. For example, you may want to enter the Client IDs of the Google apps you created for your Android and iOS builds.

  1. Go to Users > Authentication.
  2. Under Enable authentication providers, select the Google check box.
  3. Click Add Client ID and then enter the string provided by Google.

    For Android devices, this is typically the "Client ID for Web application" of the web application that Google auto-generates for each of your Android applications. For iOS devices, this is typically the "Client ID for iOS" (and not the "iOS URL scheme"). Example: Both have the following format: 28921193406-k2oi2pbe9csg8vejqk0cf0ijc6l0p8t3.apps.googleusercontent.com

    After you configure a Client ID here, ensure that you are passing the Google ID Token (id_token) (and not the Google Access Token (access_token) to Telerik Platform. This allows Telerik Platform to verify the aud claim contained in the token against the Client ID, significantly boosting your app security.

  4. Optionally, click Add another Client ID as many times as needed, referencing all Google apps that you want.

  5. Click Save.

Due to changes to the Google OAuth policy, Telerik Platform started phasing out using embedded browsers (web-views) for OAuth requests. Instead, you must use the device's native libraries to implement Google Sign-In. Google are expected to finally block web-views for OAuth requests on April 20, 2017. You must rework your apps by that date otherwise Google Sign-In will stop working.

To implement OAuth natively in a Hybrid app, enable the Google Sign-In plugin from the Telerik Verified Marketplace. Follow the instructions that come with the plugin to properly configure your Google and the REVERSED_CLIENT_ID plugin variable (only needed for iOS). To implement OAuth natively in a NativeScript app, use the libraries recommended by Google.

Enabling Microsoft Account

Microsoft Account only requires selecting a check box. You do not need to enter additional data.

  1. Go to Users > Authentication.
  2. Under Enable authentication providers, select the Microsoft Account check box.
  3. Click Save.

Enabling Twitter

Integration with Twitter requires you to enter a Consumer Key and a Consumer Secret. Twitter issues these strings when you create a Twitter application on https://apps.twitter.com/.

  1. Go to Users > Authentication.
  2. Check the box in front of the Twitter social login provider.
  3. Enter your Consumer key and Consumer secret.
  4. Click Save.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.