Skip to content

Latest commit

 

History

History
67 lines (43 loc) · 2.59 KB

twitter.md

File metadata and controls

67 lines (43 loc) · 2.59 KB
Raw

Twitter

Overview

You can authenticate users in AM with Twitter. Before you begin, you need to sign up for a Twitter Developer account.

Steps

To connect your application to Twitter, you will:

  • Register a new application in Twitter
  • Create a Twitter identity provider in AM
  • Set up the connection in Twitter
  • Test the connection

Register a new application in Twitter

Go to +Add App in the Twitter Developer Portal.

  1. Give your application a name.
  2. Click Complete.

{% hint style="info" %} Twitter will generate an API Key and API Secret Key for your application. Make a note of them for later use. {% endhint %}

Create a Twitter identity provider

  1. Log in to AM Console.
  2. Click Settings > Providers.
  3. Click the plus icon plus icon.
  4. Select Twitter as your identity provider type and click Next.

{% hint style="info" %} Ensure you have the API Key and API Secret generated by Twitter to hand. {% endhint %}

  1. Give your identity provider a name.

  2. Enter your Twitter API Key and API Secret Key.

  3. Click Create.

    Create Twitter IdP

{% hint style="info" %} Copy the URL in 1. Configure the Redirect URI to the right of the page. You need this value to update your Twitter application settings in the next section. {% endhint %}

Set up the connection

Go to your Twitter application settings and edit the Authentication Settings.

  1. Enable 3-legged OAuth.
  2. Add a Callback URLs with the Redirect URI created in the previous step.
  3. Click Save Changes.

Test the connection

You can test your Twitter connection using a web application created in AM.

  1. In AM Console, click Applications and select your social identity provider.

    Select Twitter IdP

  2. Call the Login page (the /oauth/authorize endpoint). If the connection is working you will see a Sign in with button.

    If the button is not visible, there may be a problem with the identity provider settings. Check the AM Gateway log for more information.

    Sign in Options