# Set up SSO

*This feature requires the SonarQube Cloud Enterprise license.* 

For more information about SSO, see [SSO and provisioning](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning.md).

{% hint style="info" %}
To set up SSO through Okta’s Express Configuration, see [Using Okta Express Configuration](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/using-okta-express-configuration.md).
{% endhint %}

To set up SSO in your enteprise, you must be the administrator of the enterprise in SonarQube Cloud.

{% hint style="warning" %}
**If you don't intend to use SCIM provisioning, you must first manage the user groups and permissions in your organizations as described in** [#if-using-jit](#if-using-jit "mention") **below**.
{% endhint %}

## Start the SSO setup assistant

1. In SonarQube Cloud, retrieve your enterprise. See [Retrieving and viewing your enterprise](/sonarqube-cloud/administering-sonarcloud/managing-enterprise/retrieving-and-viewing-your-enterprise.md) for more details.
2. Go to **Administration** > **SSO & Provisioning**. The **SSO & Provisioning** page opens.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/Zdt1Z7ETg1IGHDruQ5hc" alt="Select the Setup configuration button."><figcaption></figcaption></figure>

3. In the top-right corner, select **Setup configuration**.
4. In the bottom-right corner, select **Get Started**. The **Configure Your Connection** page opens.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/FtIxmYPDnD7hXiC12Yrf" alt="Select Single Sign-On to start the SSO setup."><figcaption></figcaption></figure>

5. Select **Single Sign-On**. The SSO setup assistant opens.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/PYC1NJDpBfXwVwpDqVNC" alt="Select Custom OIDC."><figcaption></figcaption></figure>

6. Select your identity provider or protocol, and select **Next**.

The SSO setup assistant opens. Follow the instructions below depending on your selection:

* [#okta-oidc](#okta-oidc "mention")
* [#related-pages](#related-pages "mention")

## Okta OIDC&#x20;

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/zFytD7f5tzaueLKKm9dk" alt="SonarQube Cloud&#x27;s SSO setup assistant for Okta OICD."><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Create application

1. In Okta, go to **Applications** > **Applications** and select **Create App Integration**.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/4T6cZk0XGUQ73VguW2JM" alt="Select OIDC - OpenID Connect."><figcaption></figcaption></figure>

2. In the dialog:
   1. In **Sign-in method**, select **OIDC - OpenID Connect**. The **Application type** section shows up.
   2. In **Application type**, select **Web application**.
3. Select **Next**.
4. Fill in the fields and options as described below.
   * **General settings:**
     * **App integration name**: the SonarQube Cloud application name.

       Example: SonarQube Cloud.
   * **Sign-in redirect URIs**: Copy-paste the **Callback URL** field value from the setup assistant.
   * **Assignments**\
     Select the following options:
     * **Controlled access** > **Allow everyone in your organization to access**
     * **Enable immediate access** > **Enable immediate access with Federation Broker Mode**
5. Select **Save**.
6. In the setup assistant, select **Next** to go to the step **2. Configure Connection**.
   {% endstep %}

{% step %}

### Configure connection

1. In Okta’s SonarQube Cloud application, go to **General > Client Credentials.**
2. Copy the value of the **Client ID** field.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/5WhsU3HePsOaIBsrRQC6" alt="Use the copy tool to copy the Client ID."><figcaption></figcaption></figure>

3. Paste the copied value to the **Client ID** field in the setup assistant page.
4. Go back to your Okta's SonarQube Cloud application and copy the client secret.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/DZ4LCYS1QXPHvVmlgdB1" alt="Select the copy tool in front of the secret value."><figcaption></figcaption></figure>

5. Paste the copied value to the **Client Secret** field in the setup assistant page.
6. Go back to Okta and select your account / name in the top-right corner.
7. Copy your Okta organization URL / domain.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/wE8bZnDDCSqVlvoJ2wZt" alt="Select your account / name in the top-right corner and copy your Okta org URL."><figcaption></figcaption></figure>

8. Paste the copied value to the **Okta Domain** field in the setup assistant.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/6tNr0idVezeAOhZeKxXL" alt="Step 2 of the Okta OIDC setup assistant."><figcaption></figcaption></figure>

9. In the bottom right corner of the assistant, select **Create Connection** and then **Proceed.** SonarQube Cloud is trying to connect to your Identity Provider. If the connection is established, the assistant moves to step **3. Claims Mapping**.
   {% endstep %}

{% step %}

### Claims Mapping

1. In your Okta’s SonarQube Cloud application, go to **Sign On.**
2. Go down to the **Token claims** section and open the **Show legacy configuration** panel.
3. Select **Edit**.
4. Set the fields as follows:
   * Groups claim type: **Filter**
   * Groups claim filter:
     * First field: `groups` &#x20;
     * Second field: Select **Matches regex** and set the value to **`.*`**&#x20;

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/4m3BFPPc4stSCXCWnrCs" alt="Edit the Group Claims."><figcaption></figcaption></figure>

5. Select **Save**.
6. In the SonarQube Cloud's setup assistant, select **Next** to go to the step **4. Assign Access**.&#x20;
   {% endstep %}

{% step %}

### Assign Access

1. In your Okta’s SonarQube Cloud application, go to **Assignments**.
2. Select **Assign**, then **Assign to Groups**.
3. Select the groups to assign to the application.
4. Select **Done**.
5. In the SonarQube Cloud's setup assistant, select **Next** to go to the step **5. Test SSO**.&#x20;
   {% endstep %}

{% step %}

### Test SSO

1. Select the **Test Connection** button. The test is started and the results are displayed on the page.
2. Verify the JSON response. In particular, verify that the email and groups attributes are correct. If the test was successful, select **Enable Connection** and **Proceed**.
3. If you want to set up SCIM provisioning, select **Provisioning** to open the SCIM provisioning setup assistant. See [Set up SCIM](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-scim.md) for more details.\
   Otherwise, enable the connection by selecting the **Enable Connection** button in the top-right corner.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/eIqRfqWpFeNONkMbY9N4" alt="To enable your SSO connection, select the Enable Connection button."><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Terminate

Terminate your SSO setup. See [Complete SSO setup](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/complete-setup.md).
{% endstep %}
{% endstepper %}

## Custom SAML <a href="#related-pages" id="related-pages"></a>

{% stepper %}
{% step %}

### Create and set up the SonarQube Cloud application in your identity provider

This step depends on your identity provider.

<details>

<summary><strong>Okta</strong></summary>

1. In Okta, under **Applications**, select **Create App Integration**.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/AJixhSReUlDx2YvtL3NM" alt="Select SAML 2.0"><figcaption></figcaption></figure>

2. In the dialog, select **SAML 2.0**.
3. Select **Next**.
4. Fill in the fields and options as described below.
   * **General settings:**
     * **App name**: SonarQube Cloud application name.

       Example: SonarQube Cloud.
     * **App visibility: Do not display application icon to users**: Select this option. (This is because SonarQube Cloud doesn’t support IdP-initiated SSO)
   * **SAML settings:**
     * **Single sign on URL**: Copy-paste the **Single Sign-On URL** field value from the setup assistant.
     * **Audience URI (SP Entity ID)**: Copy-paste the **Service Provider Identity ID** field value from the setup assistant.
     * **Response**: `Signed`
     * **Assertion Signature**: `Signed`
     * **Signature Algorithm**: `RSA-SHA256`
   * *For assertion encryption:*
     * **Assertion Encryption**: If you want to enable assertion encryption, select **Encrypted** and fill in the fields below.
     * **Encryption Algorithm**: Select `AES256-GCM` for high security.
     * **Key Transport Algorithm**: `RSA-OAEP`
     * **Encryption Certificate**: The public X.509 certificate used by the identity provider to authenticate SAML messages.

{% hint style="danger" %}
Only a single sign-on URL is allowed. Attempting to configure URLs in **Other Requestable SSO URLs** will lead to errors in your SSO setup.
{% endhint %}

5. In the **Feedback** dialog, select **Finish** to confirm the creation of the SonarQube Cloud application.
6. In the setup assistant, select **Next** to go to the step **2. Configure Connection**.

**2. Configure Connection**

1. In Okta’s SonarQube Cloud application, go to **Sign On** > **Settings** > **Sign on methods**. Copy the value of the **Metadata URL** field

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/DFRq1GNhGRBRtxWLr9fb" alt="Select the Copy tool to copy the Metadata URL."><figcaption></figcaption></figure>

2. Paste the copied value to the **Metadata URL** field in the **Automatic** tab of the setup assistant page.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/EPv8zRm5iz9JLz5Ql9IJ" alt="Open the Automatic tab."><figcaption></figcaption></figure>

3. In the assistant, select **Create Connection** and **Proceed.** SonarQube Cloud is trying to connect to your Identity Provider. If the connection is established, the assistant moves to step **3. Attribute Mapping**.

**3. Attribute Mapping**

1. In Okta’s SonarQube Cloud application, go to **Sign On.**
2. Go down to the **Attribute statements** section and open the **Show legacy configuration** panel.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/SlqqZnrhXRoIl1sfDNZ0" alt="Go down to the Attributes statements section and select the link in Learn more."><figcaption></figcaption></figure>

3. Select **Edit.**
4. In **Profile attribute statements**, add the attributes for Name, Login, and Email, and in **Group Attribute Statements**, add the attribute for Groups, as described below.
   * Name attribut&#x65;**:**
     * **Name**: Copy the attribute's **Mapping** value from the assistant (use the Copy tool).
     * **Name format**: `Unspecified`
     * **Value**: `user.firstName`
   * Login attribute:
     * **Name**: Copy the attribute's **Mapping** value from the assistant (use the Copy tool).
     * **Name format**: `Unspecified`
     * **Value**: `user.login`
   * Email attribute:
     * **Name**: Copy the attribute's **Mapping** value from the assistant (use the Copy tool).
     * **Name format**: `Unspecified`
     * **Value**: `user.email`
   * Groups attribute:
     * **Name**: Copy the attribute's **Mapping** value from the assistant (use the Copy tool).
     * **Name format**: `Unspecified`
     * **Filter**: Select `Matches regex` and set the value to **`.*`**

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/mONZIp0kuCDbuuATWR19" alt="Select Save."><figcaption></figcaption></figure>

5. Select **Save**.
6. In the SonarQube Cloud's setup assistant, select **Next** to go to the step **4. Test SSO**. See [#test-the-sso-connection](#test-the-sso-connection "mention").

</details>

<details>

<summary><strong>Microsoft Entra ID</strong></summary>

{% hint style="warning" %}

* Group synchronization doesn’t work with Microsoft Entra ID’s nested groups.
* Microsoft Entra ID’s 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 the user is in.
  {% endhint %}

Proceed as follows:

1. In Microsoft Entra ID, go to **Applications** > **Enterprise applications** > **All applications**.
2. Select **New application** and then **Create your own application**.

{% hint style="danger" %}
Make sure you choose **Create your own application**. Do not select the non-affiliated **Sonarqube** Microsoft Entra Gallery app, which contains configurations that may prevent proper integration.
{% endhint %}

3. Fill in the name and select the **Integrate any other application you don’t find in the gallery** option.
4. Select **Create**.
5. From the **Manage** section of the SonarQube Cloud application, go to **Single sign-on** > **SAML**.
6. In the **Basic SAML Configuration** section, select **Edit,** fill in the **Identifier** and the **Reply URL** fields as described below, and save:
   * **Identifier (Entity ID)**: Copy-paste the **Service Provider Identity ID** field value from the setup assistant.
   * **Reply URL (Assertion Consumer Service URL)**: Copy-paste the **Single Sign-On URL** field value from the setup assistant.
   * **Sign On URL (Optional)**: Until IdP initiated SSO is available, you can use this URL: `https://sonarcloud.io/login/sso?enterprise_key=<enterprise_key>`.

{% hint style="danger" %}
Only a single reply URL is allowed. Attempting to configure multiple reply URLs will lead to errors in your SSO setup.
{% endhint %}

7. In the setup assistant, select **Next** to go to the step **2. Configure Connection**.

**2. Configure Connection**

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/EPv8zRm5iz9JLz5Ql9IJ" alt="Open the Automatic tab."><figcaption></figcaption></figure>

1. In your SonarQube Cloud application in Microsoft Entra ID, go to **SAML Certificates**. Copy the value of the **App Federation Metadata Url** field and paste it into the **Metadata URL** field in the **Automatic** tab of the setup assistant page.
2. In the assistant, select **Create Connection** and **Proceed.** SonarQube Cloud is trying to connect to your Identity Provider. If the connection is established, the assistant moves to step **3. Attribute Mapping**.

**3. Attribute Mapping**

1. In Microsoft Entra ID, go to he **Attributes & Claims** section of your SonarQube Cloud application.
2. Remove the namespaced attributes added by Microsoft Entra ID and listed in the **Additional claims** section.
3. Select **Add new claim** and define a claim for the Email attribute. This attribute is used to manage the email of the user.
   * In **Name**, paste the name copied from the Email's **Mapping** value in SonarQube Cloud's setup assistant.
   * In **Source attribute**, select `user.mail` .

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/YAyWOOZU49EEJjd2f6A9" alt="In Name, paste the name copied from the Mapping value in SonarQube Cloud&#x27;s setup assistant."><figcaption></figcaption></figure>

The figure below shows the setup assistant of SonarQube Cloud. Use the copy tool to copy the **Mapping** value.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/9W0nELHc2FnXa1OtAuT9" alt="Use the copy tool to copy-paste the Mapping value of each attribute to your identity provider."><figcaption></figcaption></figure>

2. The same way, define a claim for the Login attribute. This attribute is the unique name used to identify the user in SonarQube Cloud. In **Source attribute**, select `user.userprincipalname`.
3. The same way, define a claim for the Name attribute. This attribute is the full name of the user. In **Source attribute**, select `user.givenname` or your own user name attribute.

{% hint style="info" %}
The default list of attributes includes `user.givenname` (first name) and `user.surname` (last name). If you prefer to show the full name, you must create a new claim in MS Entra ID.
{% endhint %}

4. Select **Add a group claim** to define the Groups attribute. This attribute is used for automatic group synchronization. Set the parameters as follows:
   * **Which groups associated with the user should be returned in the claim?**: **Groups assigned to the application**
   * **Source attribute**: **Cloud-only group display names** or (if using on-prem Active Directory for group synchronisation) **sAMAccountName**
   * **Emit group name for cloud-only groups option**: If you use sAMAccountName, select the option. Otherwise, ignore the option.

The figure below shows a group attribute definition example.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/lNT1TyukkndT4AEAuQCF" alt="Select the Groups assigned to the application option."><figcaption></figcaption></figure>

Save. The option to add a group will be unavailable and the group attribute will be listed with the other attributes in the **Additional claims** section as illustrated below.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/phyqgw73rl47F5zc8CSw" alt="Check that you have correctly defined the attributes listed in Additional claims."><figcaption></figcaption></figure>

5. In the setup assistant, select **Next** to go to the step **4. Test SSO**. See [#test-the-sso-connection](#test-the-sso-connection "mention").

</details>

<details>

<summary><strong>JumpCloud</strong></summary>

1. In JumpCloud, go to **SSO Applications** and select **+ Add New Application.**

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/zdaNFbMvOJTZaoKMUGXw" alt="Select Add New Application to create your SonarQube Cloud application in JumpCloud."><figcaption></figcaption></figure>

2. Select Custom **Application** and select **Next.**

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/PZxJhxGxp415yPSk0HiP" alt="To create your SonarQube Cloud app in JumpCloud, select Custom Application."><figcaption></figcaption></figure>

3. Click **Next**.
4. Select Manage **Single Sign-On (SSO)** and **Configure SSO with SAML**, and select **Next**.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/8WM5Eo3VzUArS17wEkVR" alt="Select Manage Single Sign-On (SSO) and Configure SSO with SAML."><figcaption></figcaption></figure>

5. Enter a display label and select **Save Application**. The application is created.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/kVzOxPYUCXizyus0epSH" alt="Enter a display lable and select the Save Application button."><figcaption></figcaption></figure>

6. Select **Configure Application**.
7. In the **SSO** tab, in the **Configuration Settings** section, set the parameters as described below:
   * **IdP Entity ID**: Don't change the default value.
   * **SP Entity ID**: Copy-paste the **Single Sign-On URL** field value from the setup assistant.
   * **ACS URL**: Copy-paste the **Single Sign-On URL** field value from the setup assistant to **Default URL**.

{% hint style="danger" %}
Only a single ACS URL is allowed. Attempting to configure multiple ACS URLs will lead to errors in your SSO setup.
{% endhint %}

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/4WB7R6rFx0VDW5YSOsWP" alt="Set the SP Entity ID and Default URL fields with the SSO URL value from SonarQube Cloud."><figcaption></figcaption></figure>

8. In **JumpCloud Metadata** in the same section, select the **Copy Metadata URL** button.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/uN4lqMYuEcVnBzWDUlZL" alt="Select the Copy Metadata URL button."><figcaption></figcaption></figure>

9. In SonarQube Cloud's SAML SSO setup assistant, go the step **2. Configure Connection** and paste the copied value to **Metadata URL** in the **Automatic** tab.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/wg352FEWkX18A8yol6P1" alt="Paste the value copied from JumpCloud to Metadata URL."><figcaption></figcaption></figure>

10. Select **Create Connection** and then **Proceed.**
11. In SonarQube Cloud's SAML SSO setup assistant, go the step **3. Attribute Mapping**.
12. In the **SSO** tab of the JumpCloud's application, go to the **Attributes > User Attributes** section and add three new attributes with the values described below:
    * Name attribute:
      * **Service Provider Attribute Name**: Paste the name copied from the **Mapping** value in SonarQube Cloud's setup assistant.
      * **JumpCloud Atttribute Name**: `username`
    * Login attribute:
      * **Service Provider Attribute Name**: Paste the name copied from the **Mapping** value in SonarQube Cloud's setup assistant.
      * **JumpCloud Atttribute Name**: `displayname`
    * Email attribute:
      * **Service Provider Attribute Name**: Paste the name copied from the **Mapping** value in SonarQube Cloud's setup assistant.
      * **JumpCloud Atttribute Name**: `email`
13. Under the **Constant Attributes** section, select the **Include Group Attribute** option. Copy the group attribute name from the assistant and paste it into **Groups Attribute Name**.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/1WyGEcltWUGP750wt0ol" alt="Add and configure user attributes and a group attribute."><figcaption></figcaption></figure>

14. Select **Save**.
15. In SonarQube Cloud's SAML SSO setup assistant, select **Next** to go to step **4. Test SSO**. See [#test-the-sso-connection](#test-the-sso-connection "mention") below.

</details>

<details>

<summary><strong>Other identity providers</strong></summary>

1. Create the SonarQube Cloud application in your identity provider.
2. Copy the **Service Provider Identity ID** field value from the setup assistant and paste it into the corresponding field in your identity provider.
3. Copy the **Single Sign-On URL** field value from the setup assistant and paste it into the corresponding field in your identity provider.

{% hint style="danger" %}
Only a single sign-on URL is allowed. Attempting to configure multiple sign-on URLs in your identity provider will lead to errors in your SSO setup.
{% endhint %}

4. In SonarQube Cloud's SSO setup assistant, select **Next** to go to the step **2. Configure Connection**.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/39R3FdWIjzGEXmLqPFe3" alt="The first step of the SonarQube Cloud&#x27;s SAML SSO setup assistant is Create Application."><figcaption></figcaption></figure>

**2. Configure Connection**

The operation is different depending on whether your identity provider supports the SAML metadata URL field (URL used by SonarQube Cloud to access metadata information) or not.

**Metadata URL supported**

1. In your SonarQube Cloud application in your identity provider, copy the value of the field corresponding to the SAML metadata URL .
2. Paste it into the **Metadata URL** field in the **Automatic** tab of the setup assistant page.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/EPv8zRm5iz9JLz5Ql9IJ" alt="Open the Automatic tab."><figcaption></figcaption></figure>

3. In the assistant, select **Create Connection** and **Proceed.** SonarQube Cloud is trying to connect to your Identity Provider. If the connection is established, the assistant moves to step **3. Attribute Mapping**.

**Metadata URL not supported**

1. In the assistant, select the **Manual** tab.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/3sIqrxnTA7vsffabvCI8" alt="Open the Manual tab."><figcaption></figcaption></figure>

2. In your identity provider, copy the value of the SSO login URL field and paste it into **Single Sign-On Login URL** in the assistant.
3. In your identity provider, download the certificate and upload it to the assistant.
4. In the assistant, select **Create Connection** and **Proceed.** SonarQube Cloud is trying to connect to your Identity Provider. If the connection is established, the assistant moves to step **3. Attribute Mapping**.

**3. Attribute Mapping**

1. In your identity provider, create the attributes for Name, Login, Email, and Groups (the group attribute is used for automatic group synchronization). To do so, for each attribute, copy the attribute's **Mapping** value from the assistant (use the Copy tool) and paste it into the attribute’s name field in your identity provider.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/nTe7kCO8VcWCBWVPeddW" alt="Select Next to go to the next step."><figcaption></figcaption></figure>

2. In the assistant, select **Next** to go to step **4. Test SSO**. See [#test-the-sso-connection](#test-the-sso-connection "mention").

</details>
{% endstep %}

{% step %}

### Test the SSO connection

1. In your identity provider, assign the user groups to the SonarQube Cloud application (to be able to perform the test, at least one group or user must be assigned).
2. In the SonarQube Cloud's setup assistant, select the **Test Connection** button. The test is started and the results are displayed on the page as illustrated below.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/H7WtcW7LEg6kndtvaeLv" alt="Before you finish step 2 configuring your connection using SonarQube Cloud’s setup assistant, test and enable your configuration."><figcaption></figcaption></figure>

3. If the test was successful, select **Enable Connection** and **Proceed**.
4. If you want to set up SCIM provisioning, select **Provisioning** to open the SCIM provisioning setup assistant and follow the setup instructions. See [Set up SCIM](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-scim.md) for more details.\
   Otherwise enable the connection by selecting the **Enable Connection** button in the top-right corner.

<figure><img src="/spaces/KXW79zfYFiA8incTvwZK/files/eIqRfqWpFeNONkMbY9N4" alt="To enable your SSO connection, select the Enable Connection button."><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Terminate

Terminate your SSO setup. See [Complete SSO setup](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/complete-setup.md).
{% endstep %}
{% endstepper %}

## If using JIT provisioning (Verify groups and permissions) <a href="#if-using-jit" id="if-using-jit"></a>

If you don't use SCIM provisioning with SSO, [Just-in-Time provisioning](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/about.md#just-in-time) will apply. In that case, you must verify your user groups to ensure the automatic group synchronization can take place properly. To do so, verify that:

* The user groups defined in your IdP service exist in the relevant organizations of your SonarQube Cloud enterprise (i.e. a group with the same (context-sensitive) name exists in the relevant organization(s)).
* The user groups in SonarQube Cloud have the correct permissions.

{% hint style="warning" %}
JIT SSO users' group memberships are reset to match those in your identity provider upon login. If you add a JIT SSO user to a SonarQube Cloud group that doesn't exist in the identity provider, the user will be removed from that group on their next login.
{% endhint %}

To manage the user groups in SonarQube Cloud, see [Managing user groups](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/user-groups.md).

### Verify groups  <a href="#okta" id="okta"></a>

#### With Okta

The automatic group synchronization of a group applies if the group in Okta and the corresponding group in the SonarQube Cloud organization have the same (case-sensitive) name. Note that the default SonarQube Cloud’s Members group is excluded from the synchronization.

The figure below shows on the left groups defined in Okta and on the right the corresponding groups defined in SonarQube Cloud in two different organizations (`OrgA` and `OrgB`). In this example, the SSO users belonging to `ENT_ORGA_ADMINS` will be automatically added to the corresponding `EN_ORG_ADMINS` group in SonarQube Cloud. it means that they will have access to `OrgA` with the permissions defined in SonarQube Cloud.

<div align="left"><figure><img src="/files/00wxXCZ43BqOGAQ9dzm4" alt="Okta groups (shown on left as your SSO application) map to SonarQube Cloud groups (shown on right as OrgA and OrgB) in different organizations."><figcaption></figcaption></figure></div>

#### With Microsoft Entra ID <a href="#entra-id" id="entra-id"></a>

The automatic group synchronization of a group applies if the group in Microsoft Entra ID and the corresponding group in the SonarQube Cloud organization have the same (case-sensitive) name. Note that the default SonarQube Cloud’s Members group is excluded from the synchronization.

The figure below shows on the left groups defined in Microsoft Entra ID and on the right the corresponding groups defined in SonarQube Cloud in two different organizations (`Docs-Team` and `claudiasonarova 2023`). In this example, the SSO users belonging to `Communications` will be automatically added to the corresponding `Communications` group in SonarQube Cloud. it means that they will have access to the `Docs-Team` organization with the permissions defined in SonarQube Cloud.

<div align="left"><figure><img src="/files/vWaiEmjI0nTF3GCclw5f" alt="Microsoft Entra ID groups (shown on left as your SSO application) map to SonarQube Cloud groups (shown on right as OrgA and OrgB) in different organizations."><figcaption></figcaption></figure></div>

{% hint style="warning" %}

* Group synchronization doesn’t work with Microsoft Entra ID’s nested groups.
* Microsoft Entra ID’s 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 the user is in.
  {% endhint %}

### Verify group permissions

To verify the group permissions at the enterprise level, see [Managing the enterprise-related permissions](/sonarqube-cloud/administering-sonarcloud/managing-enterprise/managing-the-enterprise-related-permissions.md).

In an organization, you can:

* Verify the groups that can create projects in the organization. See [Managing organization permissions](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-permissions.md) for more details.
* Verify the default permissions on new projects. See [Using permission templates](/sonarqube-cloud/administering-sonarcloud/managing-organization/manage-org-projects/manage-project-permissions/templates.md) for more details.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Set up SCIM](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-scim.md)
* [Complete SSO setup](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/complete-setup.md)
* [Using Okta Express Configuration](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/using-okta-express-configuration.md)
* [Editing or deleting SSO configuration](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/edit-or-delete-sso-setup.md)
* [Troubleshooting SSO and provisioning](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/troubleshooting.md)

## Related online learning

* <i class="fa-desktop">:desktop:</i> [Initial SonarQube Cloud Enterprise set up](https://www.sonarsource.com/learn/course/sonarqube-cloud/e390f0fe-64f4-4840-b74c-e63598af72f2/initial-sonarqube-cloud-enterprise-set-up)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-sso.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.