Configure and test your provider
An organization owner or administrator opens Settings → Single sign-on and saves a connection draft. Company SSO requires Team; existing self-hosted or grandfathered allocations retain their feature policy.
For Okta choose an OIDC Web Application; for Auth0 choose a Regular Web Application. Enable Authorization Code with S256 PKCE. Copy the exact callback URL from the draft into the provider, then enter its exact issuer, client ID and client secret in the authenticated ReasonTrail form. Match the token authentication method configured in your provider.
For SAML 2.0, save a draft and import its SP metadata or copy the displayed ACS URL and entity ID. Add the IdP entity ID, HTTPS sign-in URL and current public signing certificate. This profile requires signed assertions with SHA-256 or stronger and a stable NameID; it sends unsigned authentication requests and does not accept encrypted assertions or IdP-initiated sign-in.
Run Test sign-in. A successful test verifies the provider response; it does not enable the connection or link your account. Enable the verified connection explicitly. Never send client secrets or private keys through chat or support messages.
Connect your users
Invite users through the existing organization invitation flow. Each member signs in with their current ReasonTrail method, opens Settings → Single sign-on and chooses Link my company identity. Linking requires a ReasonTrail sign-in from the last ten minutes and explicit consent: the provider becomes a sign-in authority for the whole account, including private sources and any other organizations it belongs to. Use separate accounts where sign-in authority must stay separate. Platform administrators keep their existing sign-in methods and may test providers without linking. Share the company sign-in link shown in Settings after linking.
A matching email from a custom identity provider cannot acquire an existing account. SSO does not create organization membership, assign roles or widen project permissions. SCIM and automatic group provisioning are not included.
Pause or change a connection
Company sign-in sessions last up to eight hours and require current membership. Pausing the provider ends its SSO sessions. Changing identity configuration pauses it, invalidates pending sign-ins and requires another interactive test. Keep your current sign-in method available; unlinking your last usable method is refused.
OIDC and signed SAML fixtures are tested in CI. Live verification of your own Okta/Auth0 tenant is completed through Test sign-in during setup; the presets do not imply vendor certification.