Single sign-on
SSO setup guides
Each guide walks through creating an application in the identity provider, entering OrbitID's ACS URL and entity ID, mapping attributes and exporting the metadata. The same instructions are shown to your customers' IT admins inside an Admin Portal link.
SAML 2.0
- Okta
- Microsoft Entra ID
- Google Workspace
- Auth0
- OneLogin
- JumpCloud
- PingOne
- Rippling
- Microsoft AD FS
- Generic SAML – any other SAML 2.0 identity provider
OpenID Connect
- Generic OIDC – any OpenID Connect provider
Values you will need
Every SAML guide asks for two values, both filled in on the organization's setup guide in OrbitID and in its Admin Portal:
| Value | Production | Testing |
|---|---|---|
| ACS URL | https://app.orbitid.com/api/oauth/saml | https://app.orbitid.com/api/oauth/sandbox/saml |
| SP Entity ID | https://saml.orbitid.com/sp/<id> | https://saml.orbitid.com/sandbox |
In Production every organization gets an SP Entity ID of its own, so an identity provider that signs for many apps with one certificate can't have one organization's sign-in accepted by another. Connections set up before this keep https://saml.orbitid.com, so their identity providers need no change.
OrbitID expects the id, email, firstName and lastName attributes in SAML assertions; each guide shows how to map them for that provider.

