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

# SSO (Single Sign-On)

## Overview

The Minded platform supports SAML-based Single Sign-On (SSO) as an **enterprise feature** for authentication. This allows organizations to integrate their existing identity provider (IdP) with the Minded platform for seamless and secure user authentication.

## Configuration

Setting up SSO involves exchanging configuration details between Minded (as the Service Provider) and your organization's Identity Provider.

### From Minded (Service Provider → IdP)

When initiating SSO setup, Minded will provide the following configuration details:

* **Identifier (Entity ID)**: A unique identifier for the Minded platform as a service provider
* **Reply URL**: The endpoint where your IdP will send SAML responses after authentication

### From Customer (IdP → Service Provider)

Once SSO is configured on your organization's side, you will need to provide Minded with:

* **Identity Provider (IdP) metadata**: XML metadata file containing your IdP's configuration
* **SAML signing certificates**: Certificates used to verify the authenticity of SAML assertions

## Support

To setup SSO configuration please contact the Minded support team.


---

# 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.minded.com/platform/sso.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.
