Auth0

Auth0 provides authentication and authorization solutions for web, mobile, and legacy applications.

Use Cases the Adapter Solves

• Audit User Accounts Across Your Auth0 Tenants: Automatically inventory all Auth0 users in Axonius to identify inactive, blocked, or unverified accounts and ensure they comply with your identity governance policies.
• Monitor Tenant Security Configuration: Track critical Auth0 tenant settings — such as session lifetime, legacy grant type flags, and clickjack protection — directly in Axonius to detect misconfigurations and enforce security baselines.

Asset Types Fetched

• Users, Application Settings

Data Retrieved through the Adapter

Users - fields such as: Username, Email, Display Name, Last Login, Created Date, Phone Number, Account Disabled (Blocked), Email Verified, Identities, Type

Application Settings - Fields such as session lifetime, idle session lifetime, session cookie mode, legacy API flags

Before You Begin

Ports

• TCP port 80/443

Authentication Method

• Client ID/Client Secret

APIs

Axonius uses the following Auth0 Management APIs:

• Get Users API
• Get Tenant Settings API

To get API Access tokens, see Get Management API Access Tokens for Production.

Permissions

The value supplied in Client ID must have read:users permissions to fetch assets.

For additional required permissions, see Advanced Settings.

You must do the following before configuring the Auth0 adapter connection screen:

1. Register a new machine-to-machine application with Auth0 and authorize it:Follow steps 1 to 3. In step 3, select the Auth0 Management API, and click Authorize.
2. Create credentials using the Post method: Select the Client Secret (Post) method.
3. Get a Management API token
4. Authorize the Management API to use the credentials, by enabling the settings in the screen below. (Access this page through this path: Applications → API → Management API → Machine to Machine Applications.)

   📘

   Note

   The following permissions are required for the Fetch Organization Members setting:

   • read:organization_member_roles

   • read:organizations OR read:organizations_summary

5. Once enabled, enter the updated credentials into the Adapter connection screen.

Supported From Version

Supported from Axonius version 4.7

Connecting the Adapter in Axonius

To connect the adapter in Axonius, provide the following parameters:

Required Parameters

1. Host Name or IP Address - The hostname or IP address of the Auth0 server.
2. Client ID and Client Secret - The credentials for a user account that has the Required Permissions to fetch assets.
   To obtain the Client ID and Client Secret, follow the instructions in Authentication API, using the Post method.

Optional Parameters

1. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

2. HTTPS Proxy - Connect the adapter to a proxy instead of directly connecting it to the domain.

3. HTTPS Proxy User Name - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

4. HTTPS Proxy Password - The password to use when connecting to the server using the HTTPS Proxy.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

Application Settings

The Auth0 adapter fetches application settings from the Auth0 Management API (api/v2/tenants/settings). This lets you monitor and validate security-critical tenant configuration settings directly in Axonius, including authentication requirements, session policies, and legacy API controls. |For further information refer to Auth0 Management API - Tenant Settings.

The following tenant settings are fetched:

Advanced Settings

1. Fetch User Roles - Select this option to fetch user roles. Read permissions for roles are required for this setting.
2. Fetch Organization Members - Select this option to fetch organization members as Axonius users. If Fetch User Roles is enabled, the adapter will also fetch the roles of the organization members.

3. Exclude users that are not organization members - Select this option to not fetch users that are not part of an organization.