> 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.md).

# Okta

## Integration of SSO with Okta and TrustLogix

### Create okta SSO Application

Follow these steps to create an Okta SSO application for TrustLogix:

#### Step 1: Create Okta Application

1. Navigate to **Okta** → **Applications**.
2. Click on **Create App Integration**.
3. Select **SAML 2.0 option for SSO**.
4. provide  **App Name** & optional logo.
5. Click Next for SAML configuration.
6. &#x20;Provide **Single Sign On URL** on below format.&#x20;
   1. `https://{trustlogixhostname}/api/federation/{tlx_tenant_id}/sso`
7. Provide **Audience URI (SP Entity ID)** as below format.&#x20;
   1. `https://{trustlogixhostname}/api/federation/{tlx_tenant_id}/metadata`
8. Provide **Name ID Format** as **Unspecified &** Click on **Next.**
9. Click **App type** as **This is an internal app that we have created.**
10. Click on **Finish.**

#### Step 2: Capture Metadata XML

1. Under your registered Application, Goto **Sign On** tab.
2. Under Sign On Tab, right side, there is information about **SAML2.0,** Scroll down to bottom of the page  & click on **View SAML setup instructions.**
3. It will open up the SAML information on new tab.
4. Scroll to end of the Page, There is an **Optional** section.
5. Under the **Provide the following IDP metadata to your SP provider**.
   1. Copy the XML and save it as XML file.
   2. This file will be uploaded on TrustLogix under Integrations page.

### Enable SSO in TrustLogix

Once the Okta SSO application is created, follow these steps to configure SSO in TrustLogix:

#### Step 1: Configure SSO in TrustLogix

1. Log in to **TrustLogix** using a **Tenant Root Admin** user with Super User role.
2. Navigate to the **Integrations** page.
3. Click on **Create SSO Integration**.
4. Under the **Okta** option, Click on **Integrate**.
5. Fill in the required details:
   * **Integration Name**
   * **Metadata XML** (downloaded from the Okta)
   * **Redirect URL** (from Okta application)
     * This must  be Okta Application embedded URL.
     * Go to **General** tab under registered Okta Application.
     * under **App Embed Link** option , there is application URL under the **Embed Link** , provide this URL as redirect URL on TrustLogix.
6. Save the integration.

#### Step 2: Test SSO Login

1. Assign a user to the Okta application.
2. Create a user with the same email address in TrustLogix.
3. Log in using SSO to verify successful authentication.

***

By following these steps, TrustLogix will be successfully integrated with Okta for SSO. To enable user provisioning from Okta refer User Provisioning section.


---

# 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.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.
