# SailPoint Auth0 Connector Documentation

> Auth0 Connector Documentation

# Documentation

# Connecting SailPoint and Auth0

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Auth0 host URL into the **Base URL** field. For example, `https://dev-org-sp.us.auth0.com/api/v2`
2. Enter **Token URL**. For example, `https://dev-org-sp.us.auth0.com/oauth/token`
3. Enter **Client ID** of your Auth0 application.
4. Enter **Client Secret** your Auth0 application.
5. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Auth0

Auth0 is used as a platform to add identity and access management to applications, allowing developers to handle user authentication and authorization without building the complex infrastructure themselves. It supports features such as Single Sign-On (SSO), Passwordless Login, Multi-Factor Authentication (MFA), and Role-Based Access Control (RBAC) for managing user permissions.

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Auth0 connector supports the following:

### Account Management

- Aggregate Accounts

### Entitlement Management

- Aggregate group (roles)
- Aggregate organization

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Before configuring the connector, ensure the following setup is completed in Auth0:

1. Auth0 Tenant You must have administrator access to your Auth0 dashboard.
2. Auth0 Management API Enabled

   - Navigate to Applications → APIs → Auth0 Management API.
   - Authorize your application with the required scopes.
3. Application Created in Auth0

   - Create a Machine-to-Machine Application based on your integration requirements.
   - Make sure to note the following details:

     - Client ID
     - Client Secret
     - Domain (Tenant URL, for example: `https://dev-org-sp.us.auth0.com`)
4. API Permissions

   - Go to Applications → APIs → Auth0 Management API → Authorized Applications.
   - Toggle Authorized, open the dropdown, and select All Permissions.
   - Click Update, then Generate Access Token.
5. (Optional) Refer to the [Auth0 Management API documentation](<https://auth0.com/docs/api/management/v2?utm_source=chatgpt.com>) for additional guidance.

## Required Permissions

| Operation | Permissions |
| --- | --- |
| Read Users | `read:users` |
| Create/Update Users | `create:users, update:users` |
| Delete Users | `delete:users` |
| Read Roles | `read:roles` |
| Assign/ Unassign Roles | `update:users` |
| Read Permissions | `read:permissions` |

Recommendation: For a smoother setup experience, select all permissions for the Auth0 Management API during testing.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Auth0 connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| user\_id | Account |

### Default Account Attributes

The Auth0 connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| user\_id | Unique Auth0-generated identifier for the user |
| name | The user’s full name or primary identifier (often same as email) |
| createdAt | Timestamp of account creation |
| last\_login | Timestamp of the user’s most recent login event. |
| last\_ip | IP address from which the user last logged in |
| logins\_count | Number of times the user has logged in successfully |
| email\_verified | Shows whether the user’s email address has been verified (true/false) |
| updatedAt | Timestamp of the last time the user’s profile data was updated |
| email | The user’s registered email address |
| nickname | The user’s short name or username used |
| role\_id | Unique identifier for the role. Used internally to assign permissions to users |
| organization\_id | Timestamp of account creation |
| connection | The connection name configured in Auth0 |
| provider | Which identity provider the login came from |
| isSocial | true if it’s a social provider (like Google/Facebook), false if it’s Auth0 database or enterprise |
| provider\_id | The user’s ID within that specific provider. This ID combined with provider forms the global user ID |
| permission\_name | Fine-grained rights tied to an API or role |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

### Default Role Attributes

The Auth0 connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.

| Attribute Name | Description |
| --- | --- |
| role\_id | Unique identifier for the role. Used internally to assign permissions to users |
| role\_name | Human-readable name of the role. Helps quickly identify the role in UI or policies |
| role\_description | Brief explanation of the role’s purpose or responsibilities. Useful for documentation or onboarding |

### Default Organization Attributes

| Attribute Name | Description |
| --- | --- |
| organization\_id | Uniquely identifies an organization in Auth |
| organization\_name | The internal identifier for an organization, used by the system and API calls |
| display\_name | Friendly name of the organization displayed to users in the UI |