> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/deployment/integrations/okta.md).

# Okta

StrongDM integrates with Okta as an identity provider, handling SSO, SCIM user/group provisioning, and MFA. StrongDM can also govern access to Okta itself.

## Okta

StrongDM integrates with Okta in two directions: StrongDM can use Okta as your identity provider to authenticate and provision your team into StrongDM, and StrongDM can also treat Okta itself as a managed resource so that you can control and audit who has admin access inside Okta.

Not sure which guide you need? Use the following tables to jump to the right one.

### Use Okta to authenticate and provision StrongDM users

| I want to...                                                                       | Guide                                                                         |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Let my team log in to StrongDM with their Okta credentials (OIDC)                  | [SSO With Okta](/admin/principals/sso/okta-oidc.md)                           |
| Let my team log in to StrongDM with their Okta credentials (SAML or IdP-initiated) | [SAML for Okta](/admin/principals/sso/okta-saml.md)                           |
| Automatically create, sync, or deactivate StrongDM users from Okta (SCIM)          | [Provisioning With Okta](/admin/principals/provisioning/okta-provisioning.md) |
| Require an Okta Verify push as a second factor at StrongDM login                   | [MFA With Okta Verify](/admin/principals/mfa/mfa-okta.md)                     |

### Use StrongDM to manage access to Okta itself

| I want to...                                                                                                          | Guide                                                    |
| --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| Add Okta Admin Console as a StrongDM resource, and grant, revoke, or audit admin privileges (Okta Groups, JIT access) | [Okta (cloud resource)](/admin/resources/clouds/okta.md) |

{% hint style="info" %}
These two directions are independent in that you can set up one, the other, or both. Most organizations start with SSO or provisioning; the Okta resource guide is for teams who also want StrongDM to govern access to Okta's own admin console.
{% endhint %}


---

# 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.strongdm.com/admin/deployment/integrations/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.