> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/configurations/login-and-single-sign-on-sso.md).
# Login & Single Sign-on (SSO)
In this guide we will walk you through the steps to configure and setup your organization's SSO to let users log in with corporate credentials.
Single sign-on (SSO) is an authentication method that allows you to securely log in to multiple apps and sites using a single set of credentials. You can set up SSO to restrict which login methods users can use to access their Reo.Dev. If your team uses SSO authentication, you can set up SSO for Reo.Dev.
We support IDP-initiated SSO through two types of integrations:
* **Google and Microsoft sign-in (OAuth):** Let your team log in with their Google Workspace or Microsoft 365 work accounts. *Available on all plans.*
* **SAML SSO:** Connect your identity provider: Okta, Microsoft Entra ID or Cisco Duo. *Available on Enterprise plans only.*
If you’d prefer not to use the above methods - you can choose to login via password. If you choose this option - you can enter your login email and a link to set a password will be sent on your email. You can set the password and use it to log into Reo.Dev.
{% hint style="info" %}
Few things to note:
* By default - the password option is selected. If you’re logging in for the first time you need to set a password and then login to the platform. Once you’re logged in you can configure SSO login.
* Only users with ‘ADMIN’ role can configure SSO.
* Google and Microsoft sign-in are available on all plans. SAML SSO (Okta, Microsoft Entra ID, Cisco Duo) is available only on Enterprise plans.
{% endhint %}
### **Configuring SSO on Reo.Dev**
**Step 1:** In the Configurations tab under the Settings section on the left, click on ‘**Configure**’ under the **Login & SSO card.**
**Step 2:** Select the SSO option
**Step 3:** Select the SSO provider from the drop-down menu
{% hint style="info" %}
**Note:** SAML SSO providers (Okta, Microsoft Entra ID, Cisco Duo) are available only on Enterprise plans. If you don't see them in the drop-down menu, they aren't included in your current plan.
{% endhint %}
To set up SSO, follow the steps of your provider:
* **Google**
* Select Google from the drop-down menu.
* Then, click on Save and Enforce
* **Microsoft**
* Select Microsoft from the drop-down menu.
* Then, click on Save and Enforce SSO
* **Microsoft Entra**
* Select Microsoft Entra from the SSO provider dropdown
* Configure Reo in your Identity Provider: Copy the Reo.Dev single sign on URL, Audience URL and sign-on URL (optional) to **create a custom app** in Microsoft Entra.
* Once you’ve created a custom app, **upload the federation metadata file.** Once you upload the file, the following fields from your IDP will be auto-filled in Reo**:**
* Identity Provider Issuer URL
* Identity Provider SSO URL
* X.509 Certificate
* Then, click on Save and Enforce
{% hint style="warning" %}
Note: Only XML format files are supported. \
In case you see a failure message please check if the XML file uploaded is accurate. If the issue still persists, please reach out to your account manager to resolve this at the earliest.
{% endhint %}
Note: To add a new user, an admin must send an invitation from. Settings → Users —> Invite teammates.
* **Okta**
* Select Okta from the SSO provider dropdown
* Configure Reo in your Identity Provider: Copy the Reo.Dev single sign on URL, Audience URL and sign-on URL (optional) to **create a custom app** in Okta
* Once you’ve created a custom app, **upload the federation metadata file.** To get the XML Metadata file from Okta, follow these steps in Okta.
* Login to your Okta Dashboard and **head to the Admin console** (Ensure you have admin access)
* Navigate to **Applications > Applications**
* **Select the custom app** you created for Reo
* Head to the **Sign-on tab**
* In the SAML set-up section, click on **‘View SAML setup instructions’**
* Copy the IDP Metadata code and download it in the XML format
* **Upload the federation metadata file on Reo.** Once you upload the file, **the following fields from your IDP will be auto-filled in Reo:**
* Identity Provider Issuer URL
* Identity Provider SSO URL
* X.509 Certificate
* Then, click on **Save and Enforce**
{% hint style="warning" %}
Note: Only XML format files are supported. \
In case you see a failure message please check if the XML file uploaded is accurate. If the issue still persists, please reach out to your account manager to resolve this at the earliest.
{% endhint %}
* **Cisco Duo**
* Select Cisco Duo from the SSO provider dropdown
* Configure Reo in your Identity Provider: In the Duo Admin Panel, go to **Applications → Application Catalog**, search for **Generic SAML Service Provider**, and add a new application for Reo. Copy the SAML details from Reo into Duo.
* Next, **upload the federation metadata file.** Once you upload the file, the following fields from your IDP will be auto-filled in Reo**:**
* Identity Provider Issuer URL
* Identity Provider SSO URL
* X.509 Certificate
* Then, click on Save and Enforce
---
# 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.reo.dev/configurations/login-and-single-sign-on-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.
