> 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/10.0/instance-administration/authentication/saml/scim/scim-provisioning-with-okta.md).
# SCIM provisioning with Okta
Enable SCIM to automate user and group provisioning from Okta to SonarQube Server 10.0
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.0 documentation. For a list of all 10.0 pages, see the [SonarQube Server 10.0 page index](https://1407932334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5RUfx2eNg633cL6XgYzZ%2Fuploads%2FoPJOMr4XJ82Fq5YmEdwd%2Fsonarqube-server-10.0-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.0 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
*Automatic provisioning through SCIM is available starting in* [*Enterprise Edition*](https://www.sonarsource.com/plans-and-pricing/enterprise/)\*. \*
You can enable SCIM to automate user and group provisioning from Okta to SonarQube Server. For an overall understanding of the feature, read the SCIM [Overview](/sonarqube-server/10.0/instance-administration/authentication/saml/scim/overview.md) page.
## Prerequisites
You have a working [How to set up Okta](/sonarqube-server/10.0/instance-administration/authentication/saml/how-to-set-up-okta.md).
## Configuring SonarQube Server
To enable SCIM provisioning in SonarQube Server:
1\. go to **Administration** > **Authentication** > **SAML**
2\. Click **Automatically provision user and group with SCIM** under the **Provisioning** section. Click **Save** and validate the popup if you are sure you want to enable SCIM.
3\. Click **Save** and validate the popup if you are sure you want to enable SCIM.
SCIM is now enabled in SonarQube Server, it will handle all queries coming from Okta about users and groups.
## Configuring Okta
**Step 1**: From your Okta board, choose *your SonarQube Server application* > **General** > **App Settings** > **Edit**.
**Step 2**: Check **Enable SCIM provisioning** and click on **Save**. This will create a **Provisioning** tab.
**Step 3**: Choose the newly created **Provisioning** tab and click on **Edit.**
**Step 4**: Configure the SCIM Connection fields as follows:
* **SCIM connector base URL**: `/api/scim/v2`
* **Unique identifier field for users**: *`userName`*
* **Supported provisioning actions**: enable **Push New Users**, **Push Profile Updates** and **Push Groups**, as shown in the above picture
* **Authentication Mode**: select **HTTP Header**
**Step 5**: Click **Save**. Under the **Push Groups** tab that appears, select the groups to provision to SonarQube Server. You have two options:
* select them by name, one by one, by clicking **+ Push Groups** > **Find groups by name**.
* create a rule to match multiple groups at once. Click **+ Push Groups** > **Find groups by rule**, give it the name and the criteria of your choice, then click **Create rule**. Note that Okta does not support regular expressions here and that matching groups are immediately provisioned when the rule is created.
**Step 6:** In SonarQube Server, [Generating and using tokens](/sonarqube-server/10.0/user-guide/user-account/generating-and-using-tokens.md) from an admin account and copy the token into Okta’s **HTTP Header** > **Bearer** field\*\*.\*\* We strongly advise that the admin account used is a local one (not SCIM managed) for safety reasons.
**Step 7**: To check that the SCIM connection is valid, click on **Test Connector Configuration**. A green checkmark indicates that all the fields are properly filled.
**Step 8**: Click **Save**.
**Step 9**: In the next screen, click **Edit** and check the **Create Users**, **Update User Attributes** and **Deactivate Users** provisioning options.
Screenshot of the SCIM Provisioning to App page in Okta.
**Step 10**: Click **Save**. Okta users will be automatically provisioned with SonarQube Server.
Note that if a user gets suspended in Okta, the corresponding user account remains unchanged in SonarQube Server.
## Provisioning already assigned users
Users that are assigned before SCIM is enabled are not automatically provisioned. In the UI, an exclamation mark is displayed next to their names in the **Assignments** tab:
Screenshot showing the Provision User button in Okta.
To force the provision of these users, click on **Provision User**. The exclamation mark should disappear, meaning that the users have been provisioned.
---
# 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/10.0/instance-administration/authentication/saml/scim/scim-provisioning-with-okta.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.