Configure and troubleshoot single sign-on
Register an identity provider and understand email-domain assignment.
Table of Contents
Quantum supports identity-provider registration and domain rules for assigning newly created accounts to a provider. Domain assignment is different from the buttons people use to sign in.
What is the difference between SSO and MFA?
Single sign-on (SSO) lets a user authenticate to Quantum through the organization's identity provider. Multi-factor authentication (MFA) adds another verification factor, such as a code from an authenticator app. SSO and MFA can be used together; configuring SSO does not itself enable an MFA policy at the provider.
For SSO-managed accounts, your identity-provider administrator configures MFA requirements, enrollment, approved verification methods, and recovery. Users follow the provider's prompts during sign-in. Quantum's password and two-factor account settings are hidden for those accounts; users do not separately enroll in Quantum's password-account authenticator flow.
For Quantum password accounts, Quantum provides authenticator-app two-factor authentication using six-digit codes. Required enrollment, self-service setup, replacing an authenticator, and administrator resets follow the workspace's requirements. An SSO domain rule does not automatically migrate an existing password account, so check the account's actual Authentication method when deciding which guidance applies.
See Sign in to Quantum: MFA and SSO for requirements, enrollment instructions, sign-in troubleshooting, and lost-device recovery.
Before you begin
- You need permission to view or manage Single sign-on and access to your organization’s identity-provider administrator.
- Use the values shown in your own workspace. Do not copy ACS, audience, or redirect values from screenshots or another environment.

Choose and review a provider preset
Choose the appropriate provider preset and protocol where offered. Presets supply starting claim mappings and trust settings; review them with your identity-provider administrator before registering the provider.
| Provider preset | Protocols offered |
|---|---|
| Microsoft Entra ID | SAML and OpenID Connect |
| Okta | SAML and OpenID Connect |
| SAML | |
| OneLogin | SAML and OpenID Connect |
| AD FS | SAML |
A preset does not configure the application in your identity provider. Continue to use the ACS, audience or redirect values from your own workspace.

Validate the claims
- Compare email, username, given-name and family-name mappings with the claims your provider actually sends.
- Microsoft SAML mappings can require the full claim namespace; a short name may not identify the same claim.
- A directory expression such as
user.emailis not automatically an emitted claim name. Map the claim in the assertion or token. - Review Trust the IdP’s asserted email explicitly. Preset values differ; do not assume every provider has the same trust behavior.
- If changing provider or protocol offers to replace customized mappings, review the proposed values before confirming.
Steps
- Open Single sign-on. Under Details for your identity provider, copy the values required by your protocol. SAML uses ACS URL and Audience URI; OpenID Connect uses Redirect URI.
- Configure the Quantum application in your identity provider using those exact values. The displayed addresses may use an identity-broker domain rather than your organization’s domain; this is expected.
- Select Add new Identity Provider. Enter a Display name and select the appropriate provider preset and agreed Protocol where offered. For SAML, choose a metadata URL or XML upload and provide the provider’s metadata.
- Review Attribute mapping. Map email, username, given name, and family name claims as needed; check the preset and displayed defaults against the actual emitted claims.
- Review Trust the IdP’s asserted email with your identity owner. It allows linking by asserted email even when the provider does not mark the email verified. Enable it only where that trust is appropriate. Register the provider.
- After registration, configure approved email-domain rules in Automatic provider assignment by domain. Test with a designated account before wider rollout.

Expected result
The provider is registered and intended new accounts can be linked to it. Existing accounts retain their current sign-in method unless separately changed.
Verify the configuration
- Confirm the provider’s login button and a successful sign-in for a test account.
- Confirm claims populate the intended identity and name.
- Create a controlled test for domain assignment; a domain rule does not itself change how the sign-in buttons work.
Troubleshooting and maintenance
- For failed sign-in, compare provider metadata, ACS/audience or redirect URI, claim names, and the test account’s existing sign-in method.
- Mapping a domain does not migrate existing password accounts to SSO.
- Keep provider credentials and metadata handling within your organization’s approved identity process.
Coordinate SSO with HR provisioning
HR file mappings can control which rows create logins, while tenant SSO domain rules determine sign-in behavior. A source file's login-active or party-active field is not a substitute for configuring the identity provider and domain assignment. See Configure HR data sync and SFTP intake and Manage roles, capabilities, and access policies when coordinating identity and access.