> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/access/cloud/single-sign-on-sso/set-up-okta-sso.md).
# Set up Okta SSO
Article to help you setup an Okta for use with DecisionRules.
## **Create Application**
{% hint style="info" %}
We will mostly focus on the minumum required settings
{% endhint %}
In the Okta Admin Console navigate to **Applications** -> **Applications** -> **Create App Integration**.
From the methods, select **SAML**.
### Step 1
In the first step, you have to set up app name
Step 1
### Step 2
In the second step you have to fill in Single sign-on URL. It is
* For the **Single sing-on URL** put the address of your server (API) container with "/saml/callback/{sso\_name}" following.
* example: "*"*
* For the **Audience URI** you can put in any easily identifiable name.
Step 2
After creating the configuration, you can download the **certificate** at the Sign on tab. There is also **Sign On Url**.
### Decision Rules SSO setup
{% hint style="info" %}
[Here](/doc/access/cloud/single-sign-on-sso.md#how-do-i-set-up-a-single-sign-on-access-for-my-organization) you can find more info how set up SSO in DR application.
{% endhint %}
* Issuer - **Audience URI**
* Entry point - **Sign On URL**
* Callback Url - **Single sign-on URL**
* Certificate - **SAML Certificate**
### Adding Users
In the Okta Admin Console go to Assigments tab in Applications -> Applications -> {your\_app}. You can assign users or groups there.
---
# 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.decisionrules.io/doc/access/cloud/single-sign-on-sso/set-up-okta-sso.md?ask=&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.
