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

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.

Then the configuration

Only after the two above. See Single Sign-On for what the identity provider needs and what ShellHub expects back.

Where to go next

• Single Sign-On — Configuring it.
• Editions — Which edition has what.
• Getting Support — What to include when you ask.