> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2026.2/instance-administration/authentication/troubleshooting.md).
# Troubleshooting
Troubleshooting authentication and provisioning in SonarQube Server 2026.2.
## Users unable to use groups (SAML group number over 150)
You use SAML with Microsoft Entra ID and some users are automatically removed from groups. This may mean that you have reached the SAML group limitation (for these users, the `groups` claim is replaced by `http://schemas.microsoft.com/claims/groups.link`). Microsoft Entra ID SAML tokens have a limit regarding the number of groups a user can belong to (see the description of groups in the [Claims in SAML Token](https://learn.microsoft.com/en-us/entra/identity-platform/reference-saml-tokens#claims-in-saml-tokens) table).
In such cases, you might need to reduce the number of groups these users are in.
## Error on SAML response decryption
You have enabled the encryption of SAML assertions by your identity provider and SonarQube Server raises an error on SAML assertion decryption.
From SonarQube Server 2025.1, you must enter the public key certificate in SonarQube Server (and not only the private key). Make sure the certificate is stored in SonarQube Server as follows:
1. In SonarQube Server, go to **Administration** > **Configuration** > **General settings** > **Authentication** > **SAML**.
2. In **SAML Configuration** > **SAML**, select **Edit**. The **Edit SAML configuration** dialog opens.
3. In **Service provider certificate**, enter the certificate.
In addition, from SonarQube Server 2025.1, if you enable the encryption of SAML assertions, the SAML response, which contains the SAML assertion, must be signed. It means that the option used for SAML signature by Microsoft Entra ID and Ping Identity cannot be **Sign Assertion** (the default value). Make sure you enforce the response signature. See:
* Microsoft Entra ID: [Setup of security features](/sonarqube-server/2026.2/instance-administration/authentication/saml/ms-entra-id/optional-security-features.md#if-you-use-encryption-enforce-response-signature).
* Ping Identity: [Setup of security features](/sonarqube-server/2026.2/instance-administration/authentication/saml/ping-identity/optional-security-features.md#to-enable-the-encryption-of-saml-assertions).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/instance-administration/authentication/troubleshooting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.