> For the complete documentation index, see [llms.txt](https://olddocs.exivity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olddocs.exivity.io/advanced/integrate/sso/okta.md).

# OKTA

In order to use Okta as an Identity Provider, we need to set up a new application. The following steps will guide you through the setup and configuration:\
\
1\. Select the *Applications* section from the menu on the left and click **Applications**. A dashboard will open where you have the option to create new applications. To do so, click **Create App Integration**:

![Creating an App in Okta](/files/nkSIwgCuJ3iadEa1ZzkZ)

2\. Select the *SAML2.0* type of integration and click **Next**.

![Selecting SAML2.0 for your Exivity integration](/files/dFxho5wvRb85zLqohzlJ)

3\. Choose a relevant name for your app. You also have the option to add your logo. Click **Next** to go to the SAML configuration screen.

![Customizing the Okta app](/files/J2hqytPZT9NFjMZesmJS)

4\. Next, you must fill in the General information for the SSO URL and the SP Entity ID.&#x20;

![Filling in SSO URL and Entity ID ](/files/OYdfUbsLjtgpI1R0eGTL)

In a separate browser tab, open Exivity, navigate to **Administration** > **Settings** > **Single sing-on** and copy the values from the *Endpoints* section to your Okta configuration with the following mapping:

![Mapping between Okta and Exivity](/files/sackKjlws6u2byntoRz9)

{% hint style="success" %}
The Single Logout option is not mandatory to configure, therefore your SSO Okta integration with Exivity will work accordingly without it.
{% endhint %}

5\. Click **Next**, fill in the additional questions requested by Okta, and then finally, click **Finish**. <br>

6\. Now that you created your application, navigate to the **Sing on** tab and click the **View Setup Instructions** button in the yellow box.

![Setup instructions for SAML2 integrations with Exivity](/files/HlC4Fdoerfh4ndxCZGkN)

7\. The values from the following screen have to be inserted into the Exivity *Single sign-on* settings screen with the following mapping:

![SAML2 mapping between Okta and Exivity
](/files/6gHJLDyKhDzpeLLzhktn)

8\. Click **Update** to save your configuration.

\
9\. In order to have a completely functional configuration, we must add the Okta domain name to the CORS origins whitelist known by Exivity. Navigate to the **System** tab in the **Administration** > **Settings** menu and add your domain in the *CORS origins* field.

Your domain may look similar to: `https://`*`name`*`.okta.com`

![Adding Okta to the CORS whitelist](/files/F6pIdulhgQ0AH8NDF56u)

{% hint style="success" %}
Make sure to separate the CORS origins domains with a comma.
{% endhint %}

10\. Click **Update** to apply your new settings.

11\. Enable Single Sign-On in Exivity by navigating to **Administration** > **Settings** and then clicking on the **System** tab. Make sure the *Single Sign-On* option is set to an option including *SAML2 Authentication:*

![Enable Single Sign-On](/files/3JbJwHQHmfczZECLxSK2)

12\. Click **Update** to apply your change.

13\. Log out of the current session and you will be redirected to the login page which may look like this:

![SSO login](/files/dNOAO06CATZla2uqDs87)

14\. And by clicking on the **Login** button, you'll be taken to the Okta login screen.&#x20;


---

# 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://olddocs.exivity.io/advanced/integrate/sso/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.
