> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/configuring-vault/sso-configuration/sso-for-okta.md).

# OKTA

This article explains how to configure Single Sign-On (SSO) in AutoRABIT Vault using Okta as the SAML 2.0 Identity Provider. When SSO is enabled, users are redirected to Okta for authentication and, upon success, are taken to the AutoRABIT Vault Dashboard.

## Add the AutoRABIT Vault Application to Okta <a href="#add-vault-application-to-okta" id="add-vault-application-to-okta"></a>

### Steps:

1. Sign in to Okta as an admin. If you don’t have an Okta org, sign up at <https://developer.okta.com/signup/>.
2. Go to **Applications > Add Application**.
3. Click **Create App Integration**.
4. Choose **SAML 2.0** and click **Next**.
5. In **General Settings**:
   * Name: **AutoRABIT Vault**
   * Upload AutoRABIT Vault logo
   * Click **Next**
6. In the **Configure SAML** tab:
   * **Single sign on URL:** `<instanceURL>/ARVault/saml/SSO`\
     *e.g.*: `https://vault-qa.autorabit.com/ARVault/saml/SSO`
   * **Audience URI (SP Entity ID):** `<instanceURL>/ARVault/saml/metadata`
7. Under **Attribute Statements**:

| Name                       | Value                       |
| -------------------------- | --------------------------- |
| firstname                  | `user.firstName`            |
| lastname                   | `user.lastName`             |
| customerid                 | AutoRABIT Vault customer ID |
| restrictAutoCreationOfUser | `Yes` or `No`               |

> **Note**: Customer ID is available under the **Profile** section in your AutoRABIT Vault account.

8. Click **Next**, then choose:
   * **"I'm an Okta customer adding an internal app"**
   * **"This is an internal application that we created"**
   * Click **Finish**
9. Go to the **Assignments** tab:
   * Click **Assign > Assign to People**
   * Assign users, click **Save and Go Back**, then **Done**
10. Go to the **Sign On** tab and click **Identity Provider Metadata**.
    * Save the file as XML or copy the metadata URL.

## Configure SSO in AutoRABIT Vault <a href="#configure-sso-in-vault" id="configure-sso-in-vault"></a>

1. Log in to AutoRABIT Vault
2. Navigate to **Settings > SSO Configuration**
3. Enter a name for the config and select:
   * **Metadata URL** (paste the copied link), or
   * **Metadata File** (upload the XML file)
4. Click **Activate**

> You may disable login with AutoRABIT Vault credentials by toggling off that option.

## Logging in Using SSO <a href="#logging-in-using-sso" id="logging-in-using-sso"></a>

1. On the AutoRABIT Vault login screen, click **Login with SSO**
2. Enter your **Customer ID**
3. Click **Sign in**

> You can also log in directly from your Okta dashboard by clicking on the AutoRABIT Vault application icon.

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

**Error**:\
*"Your user is not available in the account with provided customer id. Please contact the administrator to create a user for you in the account."*

**Causes**:

1. The user is not assigned to the AutoRABIT Vault app in Okta.
2. `restrictAutoCreationOfUser` is set to **Yes** and the user has not been pre-created in AutoRABIT Vault.


---

# 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://knowledgebase.autorabit.com/product-guides/vault/configuring-vault/sso-configuration/sso-for-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.