> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Auth0

> Connect Auth0 to Living Security for user, authentication, MFA, and administrative activity.

export const EgressIpAllowlistBothSets = ({system}) => <Warning>
    <strong>{system} needs two sets of addresses, not one.</strong> Living Security mints this
    integration's access token on its own infrastructure and refreshes it continuously, so setup
    traffic and sync traffic leave from different networks. Allowlist both sets in {system}, and
    keep both in place — this is not a setup-only requirement.
    <br />
    <br />
    <strong>Integration sync traffic</strong> — the same in every region:
    <br />
    <code>52.34.139.153/32</code>, <code>54.69.127.183/32</code>, <code>44.247.133.183/32</code>,{' '}
    <code>52.26.211.56/32</code>
    <br />
    <br />
    <strong>Platform traffic</strong> — use only the row for the region that hosts your
    organization:
    <br />
    United States: <code>98.91.60.249/32</code>, <code>13.216.91.102/32</code>
    <br />
    European Union: <code>34.246.236.210/32</code>, <code>52.31.102.238/32</code>
    <br />
    <br />
    Allowlist only the sync set and setup never completes. Allowlist only the platform set and
    setup succeeds while every sync fails. See{' '}
    <a href="/integrations/managing/egress-ip-addresses">
      Configuring Integration Egress IP Addresses
    </a>{' '}
    for both failure signatures and the change policy.
  </Warning>;

export const PublicIntegrationNextSteps = () => <>
    <hr />
    <h2>Related resources</h2>
    <ul>
      <li>
        <a href="/signals/data-sources">Learn how integration data becomes Human Risk Management signals</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/integrations">Explore Living Security integrations</a>
      </li>
      <li>
        <a href="https://app.livingsecurity.ai/">Open the Living Security Platform</a>
      </li>
      <li>
        <a href="https://www.livingsecurity.com/request-demo/">Request a Living Security demo</a>
      </li>
    </ul>
  </>;

## Overview

Auth0 can contribute normalized user, authentication, MFA, and administrative activity. Reviewed examples include:

* `auth.login.failed` — fails to log in
* `mfa.failed` — fails MFA challenges
* `auth.login.blocked` — login blocked

See [how integration data becomes signals](/signals/data-sources).

To authenticate with Auth0 (Client Credentials), you need one key piece of information:

1. **Client ID** - A unique identifier for your client.
2. **Client Secret** - A confidential key used to authenticate the identity of the application (client).
3. **HostName** - The domain associated with your Auth0 tenant.
4. **Audience** - The audience for the token, which is your API.
5. **Organization** - The organization name or identifier you want the request to be associated with.

This guide will walk you through finding or generating these credentials within Auth0.

### Prerequisites:

* You must have an Auth0 account.

#### Step 1: Finding Your Client Credentials

1. Log in to your [Auth0](https://auth0.com/docs/authenticate/login) account.
2. Navigate to the [Application's Settings](https://manage.auth0.com/?_gl=1*1shsko2*_gcl_au*MzYwMDE4ODE4LjE3NDU5OTY3NDA.*_ga*NTkyOTQ4NzA5LjE3NDU5OTY3NDE.*_ga_QKMSDV5369*MTc0NTk5Njc0MC4xLjEuMTc0NTk5OTI5My42MC4wLjA.#/applications) page.
3. Click the **Create Application** button.

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/create_app.png" />

4. Add a unique name for your application and select **Machine to Machine Applications**

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/create_app_form.png" />

5. From the dropdown menu, select **Auth0 Management API**, then grant `read:users` and `read:logs`.

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/permissions.png" />

6. Click **Authorize** to create your new application.
7. On the Application page, navigate to the **Credentials** section. Your **Client Secret** will be displayed here, and the **Client ID** can be found at the top of the page.

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/credentials.png" />

#### Step 2: Finding Your HostName

* From the **Quickstart** tab of your newly created application, Auth0 provides an example request for obtaining an access token. Your **HostName** is the text that appears after `https://` and before `/oauth/token`.
* In the example below, the HostName is `dev-tb1x5mahjyey84y4.us.auth0.com`.

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/domain.png" />

#### Step 3: Finding Your Audience

* You can find this in the **Identifier** field of your newly created application under the **APIs** tab.

<img src="https://raw.githubusercontent.com/NangoHQ/nango/master/docs/integrations/all/auth0-cc/audience.png" />

#### Step 4: Finding Your Organization

* <Tip>This is optional and can be obtained from the **Organizations** page of your newly created application if your tenant is configured to use **Organizations**.</Tip>

#### Step 5: Enter credentials in the Living Security Platform

Once you have your **Client ID**, **Client Secret**,**HostName**, **Audience** and **Organization**:

1. Open the form where you need to authenticate with Auth0 (Client Credentials).
2. Enter your **Client ID**, **Client Secret**, **HostName**, **Audience** and **Organization** in their respective fields.
3. Submit the form, and you should be successfully authenticated.

<img style={{maxWidth: "450px" }} src="https://mintcdn.com/livingsecurity/oVkrOMkYmNevekTI/integrations/images/auth0-cc/connect-dialog.png?fit=max&auto=format&n=oVkrOMkYmNevekTI&q=85&s=46aca1349ceea75623146e3e249bad61" className="connect-dialog-img" width="576" height="564" data-path="integrations/images/auth0-cc/connect-dialog.png" />

You are now connected to Auth0 (Client Credentials).

***

<Note>Portions of this documentation are adapted from [Nango](https://nango.dev/docs/), used under the [Elastic License 2.0](https://github.com/NangoHQ/nango?tab=License-1-ov-file#readme).</Note>

## Network access

Skip this section unless your Auth0 tenant restricts Management API access by source IP address. Most tenants do not.

<EgressIpAllowlistBothSets system="Auth0" />

<PublicIntegrationNextSteps />