---
title: "Troubleshoot SSO"
canonical: "https://help.agiloft.com/space/HELP/43715734/Troubleshoot+SSO"
format: markdown
---
Use this page as a reference to help you troubleshoot and resolve SSO issues. It lists possible causes and solutions for error messages and symptoms. Unless otherwise noted, these errors appear when a user tries to access the system.

## Invalid KB or Project

`The Project/KB you are trying to access is Invalid` or `Invalid Project Name in HTTP Request`

Error messages like these indicate there's a mismatch between the Assertion Consumer Service (ACS) Endpoint in Agiloft CLM and the Reply, Audience, or ACS URL in your IdP. Common discrepancies include:

- One URL lists the port number and the other doesn't. For example: `https://example.agiloft.com:443/` versus `https://example.agiloft.com/`
- The Agiloft CLM URL has plus signs (+) in place of spaces and the IdP URL has underscores (_).

**Solution**

Edit the mismatched URL in either Agiloft CLM or the IdP to make sure they're the same, then try to log in again. To view and edit the URL in your KB, go to **Setup > Access > Configure SAML 2.0 Profiles**, edit the profile, and go to the Service Provider Details tab.

![Service Provider Details tab ACS Endpoint](media://260a1990-faf2-4e62-a5a9-74be2def294c)

## Assertion Details Missing from SAML Response

`SAML Response does not contain Assertion details. Possibly an invalid URL is used to login to Agiloft via SAML.`

This message indicates you tried to access Agiloft CLM via the ACS endpoint URL rather than the single sign-on URL. The ACS endpoint, ending with `/spsamlsso?project=KB+Name`, is where Agiloft CLM expects the SAML response. The login URL, ending with `/samlssologin.jsp?project=KB+Name`, is for user authentication.

**Solution**

Make sure all users access Agiloft CLM with the Single Sign-On URL. To view the URL, go to **Setup > Access > Configure SAML 2.0 Profiles** and edit the profile for the IdP. Then go to the Service Provider Details tab. Send this URL to all users who should log in via SP-initiated SAML SSO. If users log in from other webpages, make sure those pages also direct users to the SSO URL.

![Single Sign-On URL on Service Provider Details tab](media://24e66eea-82b7-4ce7-8c3d-25bb1fc0fdc9)

## Invalid User or User Not Found

`Invalid User <user>` or `User not found`

Messages like these mean you don't have a user record in Agiloft CLM. Only users who've been added to Agiloft CLM can use OAuth SSO.

**Solution**

Make sure each OAuth SSO user has a record in your KB, typically in the Employees table. In addition, make sure the record meets one of the following requirements depending on your IdP:

- For Microsoft OAuth, the user's Agiloft CLM Email address must match their email in Entra. Email is used to match users for identification in Entra.
- For Google OAuth, make sure the user's Agiloft CLM Email address matches their Gmail address or their Agiloft CLM Login matches their Google login. One of these conditions must be true for Google to match users for identification.

For information on adding users, see [User Management](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/926744591).

## No Value for Group or Team in SAML Attribute

`No value for user's <group_or_team> is available in SAML Attribute <attribute>`

This message means Agiloft CLM is configured to map group or team values from a SAML attribute, but the group or team name doesn't exist in your KB. Any group or team values the IdP sends have to exactly match a Group Name in the Groups table or a Team Name in the Teams table.

**Solution**

Review the group and team values the IdP sends and compare them with the groups and teams in your KB. Add to Agiloft CLM any missing group or team names. Make sure they exactly match the names used in the IdP. For instructions on adding groups, see [Creating New Groups](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718044). For instructions on adding teams, see [Creating a New Team](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43715692).

## SAML Response Not Valid

`The SAML assertion response received from Identity Provider is not valid`

This error has a few possible causes and solutions:

- If you just finished setting up the SAML integration, the certificate string copied to Agiloft CLM may be invalid because it has extra spaces or text added by the IdP or your browser.
  Open the IdP SAML metadata XML file in a text editor like Notepad. Review the contents, particularly the certificate string. If you see extra spaces, like tabs, delete them and save the changes. Now, replace the contents in Agiloft CLM with the fixed text. See [Replacing the SAML Certificate](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/971898905/Manage+SSO#replace_saml_certificate) for instructions.
- If SAML SSO has been operational but suddenly stopped working, the certificate may have expired. Or the certificate was already renewed for the IdP, but it wasn't updated in Agiloft CLM.
  Check the certificate in your IdP. If it's expired, generate a new one. If a new certificate was recently generated, compare the new certificate to the one in Agiloft CLM. If they don't match, replace the certificate in Agiloft CLM. See [Replacing the SAML Certificate](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/971898905/Manage+SSO#replace_saml_certificate) for instructions.
- If you use Entra and enabled token encryption, it's possible the SAML response isn't signed. Make sure Entra is also configured to sign the response. For information, see Microsoft's documentation on [SAML token encryption](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/howto-saml-token-encryption?tabs=azure-portal) and [signing options](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/certificate-signing-options?source=recommendations).

## Application Not Found in Directory

`Application with identifier <identifier_value> was not found in the directory <directory_name>`

This message means there's a mismatch between the Entity ID in Agiloft CLM and the Identifier or Entity ID in the IdP. Common discrepancies include:

- One application has `https://` at the beginning of the URL and the other application doesn't.
- Plus signs (+) are used to replace spaces in one application but underscores (_) are used in the other.

**Solution**

Edit the mismatched value in either Agiloft CLM or the IdP to make sure they're the same, then try to log in again. To view and edit the value in your KB, go to **Setup > Access > Configure SAML 2.0 Profiles**, edit the IdP profile, and go to the Service Provider Details tab.

![image](media://67cf19e3-6020-45ac-a990-b82b628c2348)

## Access is Blocked

`Your administrator has configured the application <IdP_application> to block users unless they are specifically granted`  
`('assigned') access to the application`

This message means users and groups haven't been granted access to the client application in the IdP.

**Solution**

Log in to your IdP and add to the client application the users and groups who should have SSO access to Agiloft CLM.

## Multivalued Attributes Not Captured

Users aren't getting assigned to multiple groups or secondary teams even though the SAML attribute contains multiple values.

This symptom may indicate the IdP is sending multivalued group or team attributes, but Agiloft CLM doesn't recognize the separator character used in the list of values. Therefore, only the first value in the list is captured.

**Solution**

Edit the “Specify character(s) that separate the list of Group/Team Names sent in SAML Assertion response” [global variable](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43713942) to define the separator used by the provider.

#### Related articles

> Macro (contentbylabel)