If you are sharing an API Key and Secret with more than one Service Provider, you will need to add an Authorized redirect URI for each Service Provider that shares the API key and secret. See this article for details of why you may want to do this. This article contains instructions for adding the Authorized Redirect URIs for social providers where appropriate. 


Note: AOL and Yahoo use OpenID so you do not need to set an API Key and Secret or an authorized redirect URI.


Note: Twitter does not support more than one Authorized Redirect URI for an integration, so you cannot share a Twitter API Key and Secret with more than one Service Provider.


To add Authorized Redirect URIs for each social provider:

  1. Make sure you have the credentials to the social provider developer console handy as you will need to update the settings there.
  2. In the Cirrus Console, choose the Service Provider from the drop-down list under the MySPs tab.
  3. Choose the social provider icon from the left nav bar
  4. Go to the API Setup Guide window on the right
  5. Scroll down to the authorized redirect URI the console has generated for that Service Provider
  6. Copy the authorized redirect URI
  7. Scroll back to the top of the API setup guide and click the link to log into the developer console for that social provider
  8. Find the place where you can add authorized redirect URIs (see below for instructions), and paste in the authorized redirect URI generated by the Cirrus console.


Facebook

Once logged in to the Facebook developers console:

Choose the Service Provider that is already integrated (the one with the API Key and Secret you are going to share with the new application).

On the dashboard, choose "settings" from the left nav bar

Choose "advanced" from the middle panel



Google
Once in the Google console, click "Enable APIs and Get Credentials Like Keys"
Choose the "Google + API"
Choose "Credentials" in the left nav bar
Choose the name of the integration in the middle panel
Paste the Authorized redirect URI you copied from the Cirrus console into the Google Cloud Platform console




Instagram

Log in to Instagram developers console

As part of Register a New Client provide the Valid redirect URIs or set it afterward by going to the Security tab of the client and adding one




LinkedIn

Log in to developer's console

Choose the application that is already integrated (the one with the API Key and Secret you are going to share with the new application).

Scroll down to field for adding redirect URIs




Twitter

Note for Twitter you can add only ONE redirect URI, so you cannot share the same API Key and Secret across multiple Service Providers when you integrate with Twitter  

Log in to developer's console

Choose settings from the top nav bar

Scroll down and paste the link into the "callback URL" box




Weibo

Log in to Open Weibo site

Select the application under My Applications

Under the Application menu select Advanced

Click edit in the OAuth2.0 authorization settings and enter the link as the Authorization callback page





WindowsLive

Log in to developer's console

Navigate to settings

Choose the API settings tab

Scroll down and enter the "redirect URLs"




REMINDER: AOL and Yahoo use OpenID so you do not need to set an API Key and Secret or an authorized re-direct URL