This document provides a comprehensive guide on how to integrate your application with Next Identity. Follow the steps outlined below to ensure a successful integration process.

To begin the integration process, log into the Next Identity console.

Once logged in, navigate to Applications on the left side menu, then choose the application that you would like to integrate with.

In the Application management screen, locate and select the environment that you will be integrating with (for example, development or production).

Within your selected environment, there will be an Integrate tab that you can select.

The following components will be displayed:

• Domain: This is the base URL that your application will use to connect to Next Identity. Ensure that you use the correct domain to facilitate secure and successful communication with Next Identity services.

• Client ID: This is the unique identifier assigned to your application.

• OIDC Endpoints: These are the specific URLs used during the authentication flow to manage user and application authentication. The following endpoints are available: Authorize, Token, Logout, Userinfo, and Well-known.

• Application Settings: This includes site name and post login redirect value.

• Redirect URIs: These are the allowed URLs that can be used as a redirect when calling the service with this client id. Your integration will not work if a redirect URI has not been set.

• Scopes and Claims: This will allow you to set the OAuth 2.0 scopes and JWT claim mappings for your application.

• SDKs: This is a collection of code samples designed to assist developers in integrating and interacting with Next Identity more efficiently.

• Application Secret Management: If applicable, this is the confidential key associated with your application’s Client ID.

To successfully integrate your application with Next Identity, follow these steps:

1. Utilize the Domain, Client ID, and Client Secret in your authentication configuration.

2. Refer to the provided SDKs to simplify integration and minimize custom development time.

3. If you are not using an SDK, you will need to implement calls to the OIDC endpoints as part of your login, logout, and token refresh workflows. More details can be found on the hosted integration endpoints in the Hosted Journeys OIDC Integration section of this knowledge base.

Always store your client credentials securely and avoid exposing them in client-side code to protect your application from unauthorized access.