Microsoft Entra ID single sign-on

Connect an Entra ID application and map group object IDs to clm.mt roles.

Connect Microsoft Entra ID.

A clm.mt owner and a Microsoft Entra administrator can set up sign-in for one organization. Keep an owner password available as a break-glass way in.

  1. In clm.mt, open Settings, Single sign-on, and choose OpenID Connect. Copy the Redirect URI.
  2. In Microsoft Entra admin center, open App registrations and create a registration for accounts in your organizational directory. Choose Web and paste the Redirect URI.
  3. On Overview, copy the Application (client) ID and Directory (tenant) ID. In Certificates & secrets, create a client secret and copy its Value immediately. Store the secret securely.
  4. In Token configuration, add the optional email claim to the ID token. The application needs an email address in an allowed domain to link a new identity. A preferred username alone is not treated as a verified email.
  5. In clm.mt, enter the client ID, secret and issuer URL https://login.microsoftonline.com/TENANT-ID/v2.0, replacing TENANT-ID with your directory ID. List the allowed email domains. Entra does not normally mark email verified; enable the trust option only if you trust your directory to control those addresses.

Groups and roles

  1. In App registrations, open Token configuration and add a groups claim to the ID token. Use group object IDs. To limit token size, choose Groups assigned to the application.
  2. Under Enterprise applications, open your application and assign the groups that need access. With this filtering option, users must be direct members of the assigned groups. Group assignment requires a suitable Entra ID license.
  3. In clm.mt, enter each group object ID and its role as GROUP-ID = viewer, GROUP-ID = operator, or GROUP-ID = admin, one per line. Owners are managed separately. If several groups match, the highest matching role applies when the person signs in. With mappings configured, a person without a matching group cannot use single sign-on.

A matching role updates the person’s organization membership at sign-in, including for other sessions. Existing sessions are not automatically revoked when group membership changes. Remove access in clm.mt when immediate revocation is needed. Automatic joining must be enabled in clm.mt for new people. If Entra reports too many groups, filter the claim to groups assigned to the application. The service does not call Microsoft Graph for group membership.

Test and troubleshoot

  1. Save the settings and use Test connection. Enable single sign-on, then test a separate user in a private browser window before requiring it for members.
  2. Check that the user has an email in an allowed domain, is directly in an assigned mapped group, and receives the expected role. If the token contains too many groups, check group filtering.
  3. Sign out of clm.mt and confirm the local session ends. This does not sign the person out of Microsoft; Entra may sign them in again while its session remains active.

Entra sign-in is awaiting a live tenant validation. Keep the owner break-glass account available while testing.