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

# External Identity Provider (SSO Federation)

1Kosmos can participate in single sign-on (SSO) in different roles depending on your scenario. Use the guide that matches your setup.

***

The role 1Kosmos plays (Service Provider, Identity Provider, or External Authentication Method) determines which side initiates and which side authenticates.

| Your scenario                                     | 1Kosmos role                         | External system            | Protocol | Guide                                                                                                                                                                                                                                      |
| ------------------------------------------------- | ------------------------------------ | -------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Sign users in to 1Kosmos using Microsoft Entra ID | Service Provider (SP)                | Microsoft Entra ID (Azure) | SAML     | [Microsoft Azure as an External Identity Provider](/integrations/authentication/external-identity-provider-sso-federation/microsoft-azure-as-an-external-identity-provider.md)                                                             |
| Sign users in to 1Kosmos using Okta               | Service Provider (SP)                | Okta                       | SAML     | [Setting Up 1Kosmos as an Identity Provider](/integrations/authentication/external-identity-provider-sso-federation/setting-up-1kosmos-as-an-identity-provider.md)                                                                         |
| Add 1Kosmos from the Okta catalog (prebuilt app)  | Service Provider (SP)                | Okta                       | SAML     | [1Kosmos as a Service Provider in Okta](/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-a-service-provider-in-okta.md)                                                                                   |
| Use 1Kosmos to sign users in to Okta              | Identity Provider (IdP)              | Okta                       | SAML     | [1Kosmos as an External Identity Provider in Okta](/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-an-external-identity-provider-in-okta.md)                                                             |
| Add 1Kosmos as an MFA method for Entra ID         | External Authentication Method (EAM) | Microsoft Entra ID         | OIDC     | [Setting up 1Kosmos as an External Authentication Method for Microsoft Entra ID](/integrations/authentication/external-identity-provider-sso-federation/setting-up-1kosmos-as-an-external-authentication-method-for-microsoft-entra-id.md) |

{% hint style="info" %}
**Note:** Just-In-Time (JIT) provisioning is not supported. Users who need to be redirected to an external Identity Provider must be pre-created within the IdP store or connected through a directory.
{% endhint %}


---

# 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.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation.md?ask=<question>&goal=<user_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.