# SAML Sign-In Fails

SAML failing on a deployment that has it configured looks like an identity provider problem, and usually is not.

## Check the license first

> **A missing or expired license does not announce itself**
>
> Nothing says “your license expired”. The sign-in simply fails, and every minute spent in the identity provider’s logs is wasted.

Open **License** in the admin console. It states which it is: no license installed, expiring soon, expired, or expired but inside its grace period. A license past its grace period stops gating in your favour, and SAML is one of the things that stops.

## Then check the edition

SAML is **Enterprise only**. It is not in Cloud, and it is not in Community — this is the one capability where Cloud is not a superset. If sign-in fails on Cloud, it is not misconfigured; the capability is not there. See [Editions](https://docs.shellhub.io/about/editions).

## Then the configuration

Only after the two above. See [Single Sign-On](https://docs.shellhub.io/manage/team/single-sign-on) for what the identity provider needs and what ShellHub expects back.

## Where to go next

- [Single Sign-On](https://docs.shellhub.io/manage/team/single-sign-on) — Configuring it.
- [Editions](https://docs.shellhub.io/about/editions) — Which edition has what.
- [Getting Support](https://docs.shellhub.io/help/support) — What to include when you ask.
