> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/sso-and-identity/onelogin.md).

# OneLogin

ThreatDefence integrates with **OneLogin** to collect authentication and identity activity logs for monitoring, threat detection, and incident response.

***

## Requirements

* Administrator access to the **OneLogin Admin Portal** (`<your_instance>.onelogin.com`)
* API credentials with read access

***

## Step 1. Create New API Credentials

1. Sign in to the **OneLogin Admin Portal**.
2. In the navigation menu, go to **Developers > API Credentials**.
3. Click **New Credential**.
4. In the *Create new API credential* dialog, configure the following:
   * **Name** — Enter a unique, descriptive name (e.g., *ThreatDefence Integration*).
   * **Read all** — Select the checkbox.
5. Click **Done**.
6. Copy the **Client ID** and **Client Secret** values and store them securely.

***

## Step 2. Provide Credentials to ThreatDefence

Send the following details to 📧 **<support@threatdefence.com>**:

* **Account Name** (unique, descriptive identifier for this integration)
* **Region** (your OneLogin region)
* **Client ID** (from Step 1)
* **Client Secret** (from Step 1)
* **Credential Expiry** (optional, if applicable)


---

# 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.threatdefence.com/siem-integrations/sso-and-identity/onelogin.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.