Okta Auth0 Log Events
Sync Type: Incremental
Overview
This source connector fetches log event entries from the Auth0 Management API.
Auth0 log events capture critical security and operational data including:
- User authentication attempts (successful logins, failed attempts, password resets).
- API access patterns and authorization decisions.
- Administrative actions performed in your Auth0 dashboard.
- System events and configuration changes.
- Security incidents such as blocked IPs or suspicious activities.
Prerequisites
- An account Auth0 portal.
- A Machine-to-Machine type application created on Auth0 portal. Click here to see the steps required to create one.
Details
This input has no backfill setting. The first sync starts from the oldest log event Auth0 still retains for your tenant. After each page of events, Monad stores the ID of the last log event it read, and later syncs continue from that event.
Limitations
- This input is restricted by rate limits.
- Monad limits requests to 16 per second by default, even when API Rate Limit is blank.
Permissions
- On the left navigation bar click on Applications under Applications menu, it will open up the Application's page.
- Click on APIs tab. Expand the Auth0 Management API option by clicking arrow icon located on extreme right.
- In the permissions section, search and select the following permissions -
- read
- read
Authentication
The following authentication options are supported by this input:
| Authentication Method | Documentation |
|---|---|
| Client ID and Client Secret (confidential applications) | Client secret authentication |
| OAuth2 access tokens | Access tokens |
Get the credentials
- On the left navigation bar click on Applications under Applications menu, it will open up the Application's page.
- Copy the Client ID.
- Head over to Settings tab and copy the Domain value.
- Head over to Credentials tab and copy the Client Secret value.
Generate Management API Access Token (If using OAuth2 Access Token Authentication)
- To ask Auth0 for a Management API v2 token, perform a POST operation to the
https://{yourDomain}/oauth/tokenendpoint, using the credentials of the Machine-to-Machine Application you created in the prerequisite step. - The payload should be in the following format -
Replace yourDomain, yourClientId and yourClientSecret with the credentials collected inCodeGet the Credentialssection. - The response will contain a signed JWT, an expiration time, the scopes granted, and the token type.
Code
- Provide this access token to the Access Token field in the Configuration of this input.
Access tokens are not refreshed
Monad never refreshes an OAuth2 access token. When the token expires (24 hours by default), the input stops with 401 errors until you replace the token. Use Client ID and Client Secret authentication for long-running inputs.
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
base_url | string | Yes | - | Base URL for the Auth0 management console |
auth_type | string | Yes | client_credentials | Authentication Type used by the input Allowed values: client_credentials (Client ID and Client Secret (Confidential Applications)), oauth2_access_token (OAuth2 Access Token). |
audience | string | No | - | Example - https://demo-dev.us.auth0.com/api/v2/ |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
rate_limit | object | No | - | Maximum outbound source-API request rate. A blank or zero value falls back to the connector's default rate-limiting behavior. Maximum 16 requests per second. See API Rate Limiting for the field format. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
client_id | secret | No | Auth0 application's Client ID |
client_secret | secret | No | Auth0 application's Client secret |
access_token | secret | No | Auth0 Management API Access Token |
Sample Audit Log
Code
Related Articles
Sync frequency
By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.