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

# Okta

HockeyStack integrates with Okta using Single Sign-On (SSO) to provide secure and streamlined access for users. Follow the steps below to set up the Okta integration.

## 1. Create an Okta OIDC App Integration

1. Log in to your Okta administrator dashboard.
2. Create a new [OIDC app integration](https://help.okta.com/en-us/content/topics/apps/apps_app_integration_wizard_oidc.htm).
3. Select OIDC as the Sign-in method.
4. Select Web application as the Application type.
5. Set up the following parameters:
   * Name: A descriptive name for your application.
   * Sign-in Redirect URIs:\
     <https://hockeystack-production.us.auth0.com/login/callback>
   * Trusted Origins:\
     <https://hockeystack.com>
   * Okta Domain:\
     Replace \<YOUR\_OKTA\_DOMAIN> with your Okta domain. For example, <https://dev-123456.okta.com>
6. After saving, Okta will generate a Client ID and Client Secret. Make sure to record these.
7. Add users to the Okta app integration: Users must be added in Okta and have a HockeyStack account to log in successfully.

## 2. Share Required Information with HockeyStack

Once you have set up your Okta OIDC App, please share the following information with the HockeyStack Team:

1. Client ID
2. Client Secret
3. Okta Domain (e.g., <https://dev-123456.okta.com>)

The HockeyStack Team will complete the provisioning process and enable SSO for your organization.


---

# 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.hockeystack.com/integrations/sso/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.