Provide callback URL

Now that you’ve created the custom IDP in Identity Cloud, you can build the callback URL to provide back to the IDP.

To complete this task, we will:

  1. Get your custom provider ID
  2. Build your callback URL
  3. Update the IDP

We’ll continue to use the same access token you provisioned earlier. This token lasts one hour - if it expires, you can go back and provision a new one.

Get your custom provider ID

Call the /custom-providers endpoint with GET method to find your custom IDP.

curl -L -X GET \
https://v1.api.REGION.janrain.com/CUSTOMER_ID/v2/config/low/services/engage-v2/apps/SOCIAL_APP_ID/custom-providers \
	-H 'Authorization: Bearer ACCESS_TOKEN'

Enter the id from your call’s response below. It is located within the _embedded.item array, and you should see the corresponding protocol, title, and ui details grouped with it.

See example response and ID

Build your callback URL

Now that you know the custom provider ID, we can build the callback URL needed by the IDP client/application.

The callback URL - also known as redirect URL/URI, Single Sign-On (SSO) URL, Direct Relay State, or Assertion Consumer Service (ACS) URL - specifies where the IDP response should be sent upon user authentication. In this case, you’ll need the IDP to send the response to your Identity Cloud social login service for processing.

Your callback URL is constructed using your Social Login App URL, your Customer ID, and your Custom Provider ID:

SOCIAL_LOGIN_APP_URL/CUSTOMER_ID.CUSTOM_PROVIDER_ID/callback

The above callback URL should look something like this: https://my-social-app.com/a12bc34d-567e-8f90-gh12-3i45jk678lm9.1abccd23-e456-7f8g-h9ij-012kl3m4n566/callback

Update the IDP

In a previous step, you may have provided a placeholder value to the IDP for the callback URL. Now that you have the real callback URL, go back to your configuration in the IDP’s developer portal and update the placeholder value with the constructed URL above.

Example: Example callback URL in IDP client configuration