> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/authentication/enterprise-sso.md).

# Enterprise Single Sign-On

{% hint style="warning" %}
Enterprise Single Sign-On is a paid add-on and is not included in the Community & Enterprise plan. Get in touch with your account executive to learn more.
{% endhint %}

## Who this applies to

This functionality is available for any Enterprise plan customer. The Management Console features an identity provider (IdP) that allows enterprise customers to federate access through their own SSO provider.

## Connecting your identity provider

Enterprise SSO extends your existing identity and access management strategy to the Management Console, so the same governance, provisioning, and offboarding controls your organization already trusts apply here as well. Centralizing authentication in your identity provider reduces the operational overhead of managing separate credentials, strengthens your security posture, and helps satisfy audit and compliance requirements around access control.

Onboarding is a managed, white-glove process. Our team partners with your stakeholders and IT organization to plan the integration, align it with your corporate security policies, and validate it end to end before go-live, minimizing disruption to your users and ensuring a smooth rollout across your enterprise.

## Supported Methods

| Method                                  | Type   |
| --------------------------------------- | ------ |
| SAML 2.0                                | Custom |
| OpenID Connect (OIDC)                   | Custom |
| Okta                                    | Native |
| Google Workspace                        | Native |
| Microsoft Azure AD (Microsoft Entra ID) | Native |
| ADFS                                    | Native |
| LDAP / Active Directory                 | Native |
| Ping Federate                           | Native |

## Multi-factor authentication

When you federate access through your own identity provider, multi-factor authentication (MFA) remains fully under your control, governed by your corporate security policies. We do not layer additional MFA on top of your custom IdP integration, so your organization retains a single, authoritative point of enforcement and a consistent audit trail across every system your identity provider protects.

MFA should not be confused with passphrases, which serve a distinct purpose: unlocking your access to your instances. For how sign-in and the passphrase work together, see [Why every sign-in asks for the passphrase](/management-console/authentication/passwords-and-passphrases.md#why-every-sign-in-asks-for-the-passphrase).


---

# 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.umh.app/management-console/authentication/enterprise-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.