> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/integrations/single-sign-on/okta/user-provisioning-from-okta.md).

# User Provisioning from Okta

### Enable User Provisioning

To enable automatic user provisioning from Okta to TrustLogix, follow these steps:

#### Step 1: Enable Auto Provisioning in TrustLogix

1. Navigate to existing Okta SSO Integration option. 
2. Click the **Enable Auto Provisioning** button in TrustLogix.
3. TrustLogix will generate a **SCIM URL** and a **Bearer Token**.
4. Copy the **SCIM URL** and **Bearer Token** for use in Okta.

#### Step 2: Configure Provisioning in Okta

1. Open the Application created for SSO in Okta
2. Go to General tab, & click on Edit 
3. Under **Provisioning** option, Select **SCIM,** Click **Save.** This will enable **Provisioning tab.**
4. Go to the **Provisioning** tab, under integration option, click on **Edit**
   1. Provide the **SCIM connector base URL** as **the TrustLogix-generated SCIM URL** from **Step-1**
   2. Provide the **Unique identifier field for users** as userName
   3. under Supported provisioning actions 
      1. Select Import New Users and Profile Updates
      2. Select Push New Users
      3. Select Push Profile Updates
   4. Under Authentication Mode, Select **Http Header** option
   5. Under HTTP Header -> Authorization -> Bearer, provide the **TrustLogix-generated token**.
   6. Click on **Test Connector Configuration**
   7. Once testing is successful, click on **Save**.

### References

* Regenerate SCIM token on expiration: <https://docs.trustlogix.io/integrations/single-sign-on/generate-scim-token>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.trustlogix.io/integrations/single-sign-on/okta/user-provisioning-from-okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.