> 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.md). # Authentication - [Custom Integrations](https://docs.1kosmos.com/integrations/authentication/custom-integrations.md) - [OIDC Application Integrations](https://docs.1kosmos.com/integrations/authentication/custom-integrations/oidc-application-integrations.md): OpenID Connect (OIDC) is an industry-standard authentication layer built on top of the OAuth 2.0 authorization protocol. OAuth 2.0 provides security through scoped access tokens. - [SAML Application Integrations](https://docs.1kosmos.com/integrations/authentication/custom-integrations/saml-application-integrations.md): The Security Assertion Markup Language (SAML) integration enables passwordless authentication for users logging into a service provider's web application. - [WS-Fed Application Integrations](https://docs.1kosmos.com/integrations/authentication/custom-integrations/ws-fed-application-integrations.md): WS-Fed (WS-Federation) Application Integration is a way to enable Single Sign-On (SSO) between an Identity Provider (IdP) and an application using the WS-Federation protocol. - [Desktop SSO](https://docs.1kosmos.com/integrations/authentication/desktop-sso.md) - [Kerberos Single Sign-On](https://docs.1kosmos.com/integrations/authentication/desktop-sso/kerberos-single-sign-on.md): 1Kosmos uses Kerberos with Active Directory (AD) to provide seamless SSO. Users authenticated on their AD network are automatically signed in to 1Kosmos applications without re-entering credentials. - [External Identity Provider (SSO Federation)](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation.md): 1Kosmos can participate in single sign-on (SSO) in different roles depending on your scenario. Use the guide that matches your setup. - [Microsoft Azure as an External Identity Provider](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/microsoft-azure-as-an-external-identity-provider.md): The steps to configure Azure as an External Identity Provider (IdP) for the 1Kosmos Service Provider (SP) using SAML (Security Assertion Markup Language) for authentication. - [Setting Up 1Kosmos as an Identity Provider](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/setting-up-1kosmos-as-an-identity-provider.md): Configure Okta as a service provider (SP) in addition to using it as an identity provider (IdP). When Okta acts as a service provider, it integrates with an external Identity Provider using SAML - [1Kosmos as a Service Provider in Okta](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-a-service-provider-in-okta.md): The steps to configure 1Kosmos as a Service Provider (SP) in Okta using SAML for authentication. - [1Kosmos as an External Identity Provider in Okta](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/1kosmos-as-an-external-identity-provider-in-okta.md): The steps to configure 1Kosmos as an External Identity Provider (IdP) with an Okta Service Provider (SP) using SAML for authentication. - [Setting up 1Kosmos as an External Authentication Method for Microsoft Entra ID](https://docs.1kosmos.com/integrations/authentication/external-identity-provider-sso-federation/setting-up-1kosmos-as-an-external-authentication-method-for-microsoft-entra-id.md): The steps to configure 1Kosmos as an External Authentication Method (EAM) for Microsoft Entra ID using OIDC. - [Pre-built Integrations](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations.md) - [Auth0](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/auth0.md): Enable passwordless, biometric login for your Auth0 users using 1Kosmos as a SAML 2.0 Identity Provider. Once connected, users authenticate with Touch ID, Face ID, or LiveID instead of a password. - [Entra EAM (Beta)](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/entra-eam-beta.md): Enable passwordless, biometric login for Microsoft Entra External Authentication Method (EAM) users using 1Kosmos as an OIDC Identity Provider. - [G-Suite](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/g-suite.md): Enable passwordless, biometric login for your Google Workspace users using 1K as a SAML 2.0 Identity Provider. Once connected, users authenticate with Touch ID, Face ID, or LiveID. - [Office 365](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/office-365.md): Enable passwordless, biometric authentication for Microsoft Office 365 using 1Kosmos as a SAML 2.0 Identity Provider — allowing users to sign in with Touch ID, Face ID, or LiveID instead of a password - [Okta](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/okta.md): Enable passwordless, biometric login for your Okta users using 1Kosmos as a SAML 2.0 Identity Provider. Once connected, users authenticate with Touch ID, Face ID, or LiveID instead of a password. - [Okta Identity Verification](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/okta-identity-verification.md): Connect Okta BYO IDV with 1Kosmos from a prebuilt AdminX tile — one guided form adds the OIDC client, auto-generates the Okta IDP config, and returns verified claims. - [OneLogin](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/onelogin.md): Integrate 1Kosmos passwordless authentication with OneLogin using SAML 2.0 — enabling biometric login with Touch ID, Face ID, or LiveID for your OneLogin users. - [Salesforce](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/salesforce.md): Enable passwordless, biometric login for your Salesforce users using 1K as a SAML 2.0 Identity Provider. Once connected, users authenticate with Touch ID, Face ID, or LiveID instead of a password. - [PingOne DaVinci Connector](https://docs.1kosmos.com/integrations/authentication/pre-built-integrations/pingone-davinci-connector.md): Integrate 1Kosmos passwordless authentication with PingOne DaVinci using the 1Kosmos OIDC connector — enabling seamless biometric login within your DaVinci authentication flows. --- # 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.md?ask=&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.