Setup Client App via Azure App registration

This page outlines the steps to configure your Azure Active Directory (AD) to work with Call Journey’s single sign-on (SSO).

Step 1: Create the App registration

From your Azure portal navigate to the “App registration”

Open

Select “+ New registration” and complete the screen that pops up

Step 2: Set the Redirect URI

Set the “Redirect URI to:

https://platform-anz.calljourney.com/login/sso/callback

Open

Note: The Redirect URI can also be set on the Authentication tab.

Step 3: Expose an API

• Go to Expose an API tab

• Under “Scopes defined by this API” click on “Add a Scope”

• On the right-hand side pane, leave the Application ID URI as provided and click Save and Continue in the bottom

• Next: on the “Add a scope” page (shown below) enter the details as below:

  • Scope name - User.Read

  • Who can consent? - Select as per your organization requirements

  • Admin consent display name - Read user data

  • Admin consent description - Allows the app to read signed-in user’s data

  • User consent display name - Read your data

  • User consent description - Allows the app to read your data

  • State - Enabled

• Once the above details are filled in click on Add Scope button to create the scope.

Step 4: Provided to Call Journey

Once the asset above is created, you need to provide the following information to Call Journey.

• Client ID – This is the “Application (client) ID” of the App Registration (Active Directory)

• Tenant ID - This is the “Directory (tenant) ID” of the App Registration (Active Directory)

• Authority URL - This is the endpoint address that represents the identity provider for authentication and authorization. It serves as the entry point for obtaining access tokens and managing user authentication for the application. In the context of Azure App Registration, this URL typically points to the Azure Active Directory (AAD) endpoint associated with your tenant or directory.

• Discovery Endpoint – This is the address of an auto-configuration service that will set up OIDC. It is known as the OpenID Connect metadata document. In Azure Active Directory this is located in the Overview Panel and can be reached by clicking the Endpoints button.

• Scope URI - The Scope URI represents the unique identifier for the application scope. This is the URI that defines the specific set of permissions or access levels required by the application. In the context of the WordBench 2.0 API, the Scope URI specifies the permissions the API will grant to applications interacting with it. This URI is configured during the Azure App Registration process under the "Expose an API" section, where custom scopes are defined to control access and ensure security compliance.