> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-a-service-provider-in-okta.md).

# 1Kosmos as a Service Provider in Okta

***

> **Roles in this integration**
>
> * **Identity Provider (IdP):** Okta
> * **Service Provider (SP):** 1Kosmos (added from the Okta prebuilt catalog)
> * **Protocol:** SAML

### Supported features

The Okta SAML integration currently supports the **SP-initiated SSO** feature.

### Configuration steps

1. Sign in to your Okta instance as an administrator.
2. Navigate to **Applications > Applications > Browse App Catalog**.
3. On the **Browse App Integration Catalog** page, select the 1Kosmos application and click **Add Integration**.
4. On the **General Settings: Required** page, enter the application name, Entity ID, and ACS URL.
5. Copy the **Entity ID** and **ACS URL** from your 1Kosmos instance (under the **External IdP Config** section) and paste them into the corresponding fields on the **General Settings: Required** page in Okta.

   > **Note:** When adding the ACS URL, it is recommended to remove the `https://` prefix.
6. Click **Done**.
7. In your Okta instance, navigate to the **Sign On** tab and copy the Metadata URL.
8. In the 1Kosmos interface, paste the Metadata URL into the **Enter Metadata URL** field and click **Import**. The **Core Configuration** tab auto-populates with the corresponding values.
9. Copy the **Sign Out** URL from the Okta instance and paste it into the **SLO URL** field in the 1Kosmos interface.
10. Click **Save**.
11. In the **Routing Policies** tab of the 1Kosmos instance, define the condition for users to exclude from the policy, enable the policy, and click **Save**.

{% hint style="info" %}
**Note:** By default, this policy applies to everyone. However, you can exclude certain users from it. Enabling this policy is optional.
{% endhint %}

### Setting up SP-initiated single sign-on

This section explains how to configure and perform SP-Initiated Single Sign-On (SSO), where the authentication flow is initiated from the Service Provider (SP) rather than the Identity Provider (IdP).

{% hint style="info" %}
**Note:** This section applies only to SAML or OIDC integrations that support app-initiated Single Sign-On (SSO), also known as Service Provider (SP) initiated SSO.
{% endhint %}

The user sign-in flow starts from the 1Kosmos sign-in page. The user enters their username, and 1Kosmos sends the authentication request to Okta (the Identity Provider) to authenticate the user.

The sign-in process is initiated from your 1Kosmos tenant:

1. From your browser, navigate to the 1Kosmos tenant sign-in page.
2. Enter your username. You are redirected to the Okta sign-in page.
3. Enter your Okta credentials and, optionally, provide your MFA as per your organization's policies. You are redirected to 1Kosmos and logged into the interface.


---

# 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.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-a-service-provider-in-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.