> 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/pre-built-integrations/auth0.md).

# Auth0

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.

***

### Prerequisites

Before starting, make sure you have:

* **AdminX portal** — Admin access to your 1Kosmos AdminX tenant. 
* **Auth0 account** — Admin access to your Auth0 tenant.
* **1Kosmos mobile app** — Installed and enrolled on iOS or Android. ([Android](https://play.google.com/store) · [iOS](https://apps.apple.com/))
  * Biometrics (Touch ID / Face ID or LiveID) must be enrolled before testing.

***

### Step 1 — Configure Auth0

{% hint style="info" %}
**Note:** These steps are performed by your Auth0 administrator.
{% endhint %}

1. Sign in to your [Auth0 dashboard](https://manage.auth0.com/).
2. Go to **Applications → Applications** and open the application you want to integrate.
3. On the **Settings** tab, copy and save:
   * **Domain URL**
   * **Client ID**
   * **Client Secret**
4. Scroll to **Application Properties** and confirm **Application Type** is set to **Regular Web Application**.
5. Scroll to **Advanced Settings → Grant Types** and check **Client Credentials**. Click **Save Changes**.
6. Go to **Applications → APIs → Auth0 Management API → Machine to Machine Applications**.
7. Find your application and toggle it to **Enabled**.
8. In the **Permissions** section, search for `create:connections`, select it, and click **Update**.

***

### Step 2 — Connect Auth0 in AdminX

{% hint style="info" %}
**Note:** These steps are performed by your AdminX administrator. Credentials entered here are **one-time use only**. 1Kosmos does not store them — rotate passwords and revoke tokens after setup.
{% endhint %}

1. Sign in to the AdminX portal and go to **Applications → Add Application**.
2. Under **Pre-built integrations**, click **Add Integration** on the **Auth0** card.
3. Fill in the following fields:

   | Field               | Value                               |
   | ------------------- | ----------------------------------- |
   | Application Name    | A display name for this integration |
   | Auth0 Domain        | Your Auth0 Domain URL (from Step 1) |
   | Auth0 Client ID     | Your Client ID (from Step 1)        |
   | Auth0 Client Secret | Your Client Secret (from Step 1)    |
4. Click **Connect**.

AdminX automatically generates the SAML Service Provider (SP) configuration in Auth0 and enables the integration.

***

### Step 3 — Test the Connection

1. Open a browser and navigate to your Auth0 domain URL.
2. You'll be redirected to the 1Kosmos AdminX login screen showing a QR code.
3. On the 1Kosmos mobile app home screen, tap **Scan QR**.
4. Scan the QR code. When prompted for location access, select **Allow only while using the app**.
5. Tap **Authenticate** and complete biometric verification (Touch ID, Face ID, or LiveID).
6. On success, you'll be logged in to your Auth0 application.


---

# 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/pre-built-integrations/auth0.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.