> 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/okta.md).

# Okta

This guide walks through how to set up Okta System Logs as a source in Scanner Collect, using direct API integration with Okta’s System Log API.

We’ll assume that you want Scanner to both store the logs in S3 and index them for search and detection.

## Create a Collect Rule

{% stepper %}
{% step %}

### Begin Setup

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 **Okta**.
  {% endstep %}

{% step %}

### Configuration

Set a Display Name, such as `my-org-okta-logs`.
{% endstep %}

{% step %}

### Authenticate with Okta

* If you’ve previously created an Okta connection, select it from the list.
* Otherwise, select **New Okta Connection** and fill in the required fields:
  * Connection Name: Give the connection a recognizable name.
  * Okta Domain: eg. `your-domain.okta.com`.
  * API Token: Generate this from your Okta admin console.

For help finding these values:

* [Find your Okta Domain](https://developer.okta.com/docs/guides/find-your-domain/main/)
* [Create an Okta API Token](https://developer.okta.com/docs/guides/create-an-api-token/main/)
  {% endstep %}

{% step %}

### Destination

* Choose the S3 Bucket where the raw Okta logs should be stored.
* (Optional) Enter a Key Prefix to organize the data path in your bucket.
  {% endstep %}

{% step %}

### Review and Create

Review all configuration settings. Any errors and/or missing fields must be resolved before completion.
{% endstep %}
{% endstepper %}

## Create an Index Rule

With the Collect Rule created, Scanner will poll the Okta System Log API every **5 minutes**, writing new events to your S3 bucket. Create an Index Rule to make those logs searchable and available for 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 %}

### Okta 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: Okta
* **Timestamp Field**: `.published`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/okta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.