> This page is for Taurus PROTECT, version v3.50.
> For other versions, use one of these documentation indexes:
> - v3.58 (default): https://taurushq.ferndocs.com/protect-capital/v3.58/llms.txt
> - v3.56: https://taurushq.ferndocs.com/protect-capital/v3.56/llms.txt
> - v3.54: https://taurushq.ferndocs.com/protect-capital/v3.54/llms.txt
> - v3.52: https://taurushq.ferndocs.com/protect-capital/v3.52/llms.txt
> - v3.50: https://taurushq.ferndocs.com/protect-capital/v3.50/llms.txt
> - v3.48: https://taurushq.ferndocs.com/protect-capital/v3.48/llms.txt
> - v3.46: https://taurushq.ferndocs.com/protect-capital/v3.46/llms.txt
> - v3.44: https://taurushq.ferndocs.com/protect-capital/v3.44/llms.txt
> - v3.42: https://taurushq.ferndocs.com/protect-capital/v3.42/llms.txt
> - v3.40: https://taurushq.ferndocs.com/protect-capital/v3.40/llms.txt
> - v3.38: https://taurushq.ferndocs.com/protect-capital/v3.38/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://taurushq.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://taurushq.ferndocs.com/_mcp/server.

# Introduction

SSO can only be configured through the Administrator role in Taurus-PROTECT.

* See [User guides](/user-guides/docs/sso) for more details.

\


# SSO - Support in Taurus-PROTECT

**SSO** (Single sign-on) is an authentication scheme that allows users to use independent applications while using a single login ID. It allows for a usage of Taurus-PROTECT as an **SP** (Service Provider) using an external **IdP** (Identity Provider) such as Okta or Azure AD.

We support two identity authentication protocols for the communication between the IdP and the SP (Taurus-PROTECT).

* **OIDC** (OpenID Connect)
* **SAML** (Security Assertion Markup Language)

Taurus-Protect also supports the **SCIM** (System for Cross-domain Identity Management) specification for users management. This makes it possible to handle the Taurus-PROTECT users lifecycle directly from the **IdP** (automatic creation/update/delete) as well as for groups/roles on a global level.

> **Warning**
>
> **Important**
>
> It is highly recommended to have a good understanding of the Taurus-PROTECT users lifecycle, key management, its operating model design and have some experience using the product without SSO before making any integration.