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

# Okta SAML

## Steps:

1. Go to the Secoda app > Settings > Security > SAML. Copy the **ACS URL** and **Entity ID** for use in the following steps.

   <figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/4aab2604-72d7-47f2-b267-59cbf46352be.png" alt=""><figcaption><p>Secoda app > Settings > Security > SAML</p></figcaption></figure>
2. In the Okta console: click the button “Create App Integration” (SAML2.0)
3. Name the app `Secoda`
4. Set the **SSO URL** and **Audience** to your personalized **ACS URL** copied from above.
5. Add the following attribute statements. While Okta marks them as optional, this step is *required*.

   ![](https://imagedelivery.net/28-eDrK8lEif6_ED0iMQeg/f1c1ee1d-d138-4962-0c4c-b669b0e33100/public)
6. Click Next.
7. Click Finish. Assign users to this application if you want them to be able to sign in.
8. Go to the Sign On tab and expand the SAML 2.0 box to see the Metadata details. Copy the **Metadata URL**
9. Navigate to the Secoda app > Settings > Security > SAML
10. Choose Okta as the **SAML Provider (IdP)**
11. Paste the link from Step 8 under **Metadata URL**. Save this configuration.

Now you can logout, click “Sign in with SAML”, and enter your domain to complete sign-in.


---

# 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.secoda.co/enterprise/saml/okta-saml.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.