> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/auth0.md).

# Auth0

This guide walks through how to set up Auth0 logs in Scanner Collect, using Auth0 log streams with custom webhooks to send logs directly to Scanner’s HTTP receiver.

## Create a Collect Rule

{% stepper %}
{% step %}

### Create a New Source

In the Scanner UI, go to the Collect tab.

* From the Overview page click the '+' icon in the upper right corner
* Select create new **Collect Rule**
* Click **Select a Source Type**.
* Choose **Auth0**.
* For Ingest Method, select **HTTP Push**.
* For Destination, select **Scanner**.

If you only want logs stored in your S3 buckets (without indexing or detection), choose AWS S3 Only. This guide assumes you’re using Scanner as the destination.
{% endstep %}

{% step %}

### Configure the Source

* Set a Display Name such as `my-org-auth0-logs`.
* Leave the Payload Format as the default: **JSON: Generic**.
  {% endstep %}

{% step %}

### Configure Authentication

* Keep the default Authentication Type: **Bearer Token**.
* Generate a **Bearer Token** and specify that here (we'll refer to it as `BEARER_TOKEN`)
  {% endstep %}

{% step %}

### Configure Destination

* Select the S3 bucket where you want raw logs delivered.
* (Optional) Enter a bucket prefix. The default is fine for most setups.
  {% endstep %}

{% step %}

### Review and Create

* Review your configuration.

After creation, Scanner will display a unique Endpoint URL like:

`https://collect.your-org-and-region.scanner.dev/receiver/v1/http/<id>`
{% endstep %}

{% step %}

### Configure in Auth0

* Log in at `auth0.com`.
* Navigate to **Monitoring** → **Log Streams.**
* Click **+ Create Log Stream**.
* Click **Custom Webhook**.
* Set a name such as `Send logs to Scanner`.
* Click **Create**.
* Set the Payload URL to the collect URL provided by scanner.
* Set Authorization Token to `Bearer ${BEARER_TOKEN}`
  * **Note:** Auth0 requires the `Bearer` prefix. If you set your generated token to `foo` in scanner, it should be set to `Bearer foo` in Auth0.
* Content Type should be `application/json` (the default)
* Content Format should be `JSON Lines` (the default)
* Set all other fields per your desired configuration.
  * Filter logs / obscure logs / start streaming logs at a specific time in the future/past.
* Click **Save**.

After creation, you can check the Health of your Auth0 Stream for any errors as reported by Auth0.
{% endstep %}
{% endstepper %}

Once routing is complete, logs will flow from Auth0 → Scanner HTTP Receiver → S3 → Scanner index.

## Create an Index Rule

Logs flow from Auth0 → Scanner’s HTTP receiver → your S3 bucket. Create an Index Rule to have Scanner index those logs for fast search and detections.

{% content-ref url="/pages/Gem9jwD4aqayN3OiChpN" %}
[Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md)
{% endcontent-ref %}

### Auth0 Defaults

When you create the Index Rule from the Collect Rule, the following defaults are pre-populated:

* **Transformations**: Add Metadata, Parse JSON Columns, ECS Normalization: Auth0
* **Timestamp Field**: `.data.date` (falls back to `.detail.data.date`)


---

# 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.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/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.