> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.46.6/built-in-connectors/okta.md).

# Okta

The Okta connector for Elimity Insights fetches users, groups and applications from Okta so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Setting up a dedicated read-only user in Okta

As usual, we recommend setting up a dedicated user in Okta for this connector. Make sure this user has read access to the users, groups and applications in your organization. Note down the hostname of your Okta organization (e.g. `example.okta.com`) for later use.

## 2. Generating an API token for the dedicated user

Having set up a dedicated user in Okta, we now need to generate an API token for authentication. Refer to [the official documentation](https://help.okta.com/en-us/content/topics/security/api.htm?cshid=ext-create-api-token#create-okta-api-token) for detailed instructions. Note down the generated token for later use.

## 3. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Okta source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>host</td><td>Hostname of your Okta organization, which you noted down in step 1.</td></tr><tr><td>API token</td><td>API token you generated in step 2.</td></tr></tbody></table>


---

# 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.elimity.com/reference-manual/v3.46.6/built-in-connectors/okta.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.