> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Okta System Logs Collector source plugin

> Receive pipeline data from Okta System Logs Collector.

export const entity_0 = "Okta System Logs Collector source plugin"

export const plugin_0 = "Okta System Logs Collector source plugin"

<Info>
  This information is for Palo Alto Networks Telemetry Pipeline, which is a standalone
  product separate from Palo Alto Networks Cortex XCOR.
</Info>

The Okta System Logs Collector [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `http_loader`, alias: `okta_system_logs`) lets you ingest data from your
Okta instances into a telemetry pipeline.

This is a
[pull-based](/ingest/pipeline/plugins/source-plugins#push-based-and-pull-based-source-plugins)
source plugin.

<Note>
  This plugin doesn't support the use of a
  [descriptive metadata name](/ingest/pipeline/plugins#descriptive-names) in the
  Pipeline Builder interface.
</Note>

<Note>
  This plugin doesn't support duplicates of itself within the same pipeline.
  Additionally, this plugin can't be used in combination with these source plugins
  within the same telemetry pipeline:

  * [Absolute](/ingest/pipeline/plugins/source-plugins/absolute)
  * [HTTP API collector](/ingest/pipeline/plugins/source-plugins/http-collector)
  * [Mandiant ASM](/ingest/pipeline/plugins/source-plugins/mandiant-asm)
  * [Signal Sciences](/ingest/pipeline/plugins/source-plugins/signal-sciences)
  * [Slack](/ingest/pipeline/plugins/source-plugins/slack)
  * [Vectra M365](/ingest/pipeline/plugins/source-plugins/vectram365)
</Note>

## Supported telemetry types

The {plugin_0} for Palo Alto Networks Telemetry Pipeline supports these telemetry types:

| Logs | Metrics | Traces |
| :-: | :-: | :-: |
| <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Palo Alto Networks Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-files)
use the items in the **Key** column as YAML keys.

### General

| Name | Key | Description | Default |
| - | - | - | - |
| **Okta Domain URL** | `url` | The URL of your Okta domain. | *none* |
| **Okta API Token** | `api_token` | Your Okta API token. | *none* |
| **Pull Interval** | `pull_interval` | The time between each API call in Okta system logs. | `10s` |

### Advanced

| Name | Key | Description | Default |
| - | - | - | - |
| **Optional Request body** | `body` | Optional request body. For example, `{"custom":"data"}`. | *none* |
| **Request Timeout** | `timeout` | The amount of time between requests. | `10s` |
| **Max Response Bytes** | `max_response_bytes` | Whether to limit the amount of bytes to read from the response body. | `1572860` |
| **Memory Buffer Limit** | `mem_buf_limit` | Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit's rules for [unit sizes](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit#unit-sizes). If unspecified, no limit is enforced. <p />For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet [workload](/ingest/pipeline/v2/configure/kubernetes/workloads) type. To learn more, see the v2 [backpressure](/ingest/pipeline/v2/configure/backpressure) guide. <p />For v3 pipelines, this parameter is independent from the [OpenTelemetry `memory_limiter` and `batch` processors](/ingest/pipeline/v3#route-data-from-fluent-bit-to-opentelemetry). | *none* |

### OAuth2

| Name | Key | Description | Default |
| - | - | - | - |
| **OAuth2 Client ID** | `oauth2_client_id` | Optional OAuth 2.0 Client ID. You need to at least pass the client ID, secret and token URL to enable OAuth 2.0 authentication. Uses the `client_credentials` flow. | *none* |
| **OAuth2 Client Secret** | `oauth2_client_secret` | Optional OAuth 2.0 client secret. | *none* |
| **OAuth2 Token URL** | `oauth2_token_url` | Optional OAuth 2.0 token URL in the formal of HTTP or HTTPS. For example, `https://example.org/oauth2/token`. | *none* |
| **OAuth2 Scopes** | `oauth2_scopes` | Optional list of additional scopes for OAuth 2.0 authentication separated by space. For example, `scope1 scope2`. | *none* |
| **OAuth2 Scopes Separator** | `oauth2_scopes_separator` | Additional parameter to pass during OAuth 2.0 authentication that separates scopes specified in OAuth 2.0 Scopes. | *none* |
| **OAuth2 Additional Params** | `oauth2_endpoint_params` | Optional additional parameters to add during OAuth 2.0 authentication. The format is a URL query string. For example, `foo=bar&bar=qux`. | *none* |


## Related topics

- [Ingest telemetry data with source plugins](/ingest/pipeline/plugins/source-plugins.md)
- [HTTP API collector source plugin](/ingest/pipeline/plugins/source-plugins/http-collector.md)
- [Absolute source plugin](/ingest/pipeline/plugins/source-plugins/absolute.md)
- [Slack source plugin](/ingest/pipeline/plugins/source-plugins/slack.md)
- [Signal Sciences source plugin](/ingest/pipeline/plugins/source-plugins/signal-sciences.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.