---
title: "Microsoft OAuth 2.0 and OIDC SSO Setup"
canonical: "https://help.agiloft.com/space/HELP/43718530/Microsoft+OAuth+2.0+and+OIDC+SSO+Setup"
format: markdown
---
Agiloft CLM supports single sign-on (SSO) with Microsoft OAuth 2.0 and OpenID Connect (OIDC) for authentication and identification. This article guides you through the steps to register Agiloft CLM as an OIDC service provider (SP) in Entra and then configure your KB to route SSO logins to Microsoft as the identity provider (IdP). It also includes instructions on how to log in with SSO after the integration and make sure other users log in with SSO as well.   

> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - To complete the setup, you need admin access to the Entra admin center with permission to configure new applications.
> ℹ️ - Users can't log in with OAuth 2.0 SSO unless they already have a user record in Agiloft CLM. Before setting up SSO, make sure each user who will use SSO has a user record in your KB. You can set up SCIM provisioning to create and update user records automatically. See [Provision Users with SCIM](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/779649034) for details.
> ℹ️ - Also make sure each user’s Email address in Agiloft CLM matches their email in Entra. The email address is used to match users for identification.

# Set Up SSO in Entra

Follow the steps below to register Agiloft CLM as an app in Entra and configure the app for use with SSO.

> ℹ️ If the options you see in the admin center or your practices for registering applications differ from those described here, refer to Microsoft's [documentation](https://learn.microsoft.com/en-us/power-pages/security/authentication/openid-settings#create-an-app-registration-in-azure) on creating an app registration to complete the task.

1. Sign in to the [Entra admin center](https://entra.microsoft.com/) as an administrator with permission to configure new applications.
2. In the tenant in which you want to add an application, go to **Identity > Applications > App registrations** and click New registration.
3. Enter a name for the app, such as Agiloft OAuth SSO.
4. Select the appropriate option for which account types can use the application. This choice depends on the IT security policy for your organization.
5. For the Redirect URI, select Web for the platform and enter the following URI: `https://HOSTNAME/ui/oauth20sso`. Replace HOSTNAME with the hostname for your Agiloft CLM instance. For example: `https://example.agiloft.com/ui/oauth20sso`. Copy this URI to a note to use later in the setup.
6. Click Register. The admin center opens the overview page for the application.
7. On the Overview page, copy the Application (Client) ID value to your note to use later in the setup.
8. Now, click Endpoints at the top of the page and copy the following values to your note:
  1. OAuth 2.0 authorization endpoint (v2) - The URI ends with `/oauth2/v2.0/authorize`
  2. OAuth 2.0 token endpoint (v2) - The URI ends with `/oauth2/v2.0/token`
9. Next, create a client secret for the app:
  1. In the app registration, click Certificates & secrets.
  2. On the Client secrets tab, click New client secret.
  3. Enter a description, select the longest available expiration date, and then click Add. When the secret does expire, you'll need repeat this step to generate a new secret and update the Client / Consumer Secret value in your Agiloft OAuth 2.0 profile as described in [Set Up SSO in Agiloft CLM](#configure_sso) below.
  4. Copy the secret value to your note. You won't be able to access it after this point.
10. Now, click Authentication in the app registration.
11. On the Settings tab under Implicit grant and hybrid flows, select ID tokens, then click Save.
12. Next, add an [optional claim](https://learn.microsoft.com/en-us/entra/identity-platform/optional-claims?tabs=appui#configure-optional-claims-in-your-application).
  1. Click Token configuration in the app registration.
  2. Click Add optional claim.
  3. Select ID as the Token type and select `email` in the list of claims.
  4. Click Add.
  5. If you get a message stating the claim requires OpenID Connect scopes to be configured, select the checkbox to turn on the Microsoft Graph email permission and click Add again.
13. Now that the app is registered, add the users and groups who need access to the application:
  1. Go Enterprise applications in the sidebar and choose the application you created.
  2. Go to Users and groups and click Add user/group at the top of the screen.
  3. Add the users and groups who need access to Agiloft CLM through single sign-on.

Now that the application is configured in Entra, you can set up SSO in Agiloft CLM.

# > Macro (anchor)

Set Up SSO in Agiloft CLM

Follow the steps below to set up SSO in your KB.

1. Go to **Setup > Access > Configure OAuth 2.0 Profiles** and click New to add a profile.
2. Leave the "Use full OAuth account name as a KB login name / email" checkbox selected.
3. Enter a name for the OAuth 2.0 provider, such as Entra.
4. For the role of this OAuth 2.0 Provider, select OAuth20_SSO.
5. Complete the remaining fields:
  1. **Redirect URI**: Overwrite the default value with the URI you noted in step 5 when setting up Entra.
  2. **Client ID / Application ID / Consumer Key**: The Application (client) ID from your note.
  3. **Client / Consumer Secret**: The Client secret from your note.
  4. **Authentication URI**: The OAuth 2.0 authorization endpoint (v2) from your note.
  5. **Token URI**: The OAuth 2.0 token endpoint (v2) from your note.
6. Click Finish to save the profile.
7. Finally, make sure each user who will log in with SSO has a user record in Agiloft CLM. Make sure their Email address in the record matches their email in Entra. The email address is used to match users for identification. For information about creating user records, see [User Management](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/926744591).

Agiloft CLM is now configured to allow SSO with Microsoft OAuth 2.0 and OIDC. Proceed to [Log in with SSO](#sso_login) for details on how to log in.

# > Macro (anchor)

Log in with SSO

> Macro (include)

# > Macro (anchor)

Force SSO Login

> Macro (include)

#### Related articles

> Macro (contentbylabel)