multi-router.aidocs

Single Sign-On

TroubleshootingEnterprise

SSO setup and sign-in errors, with their causes and fixes.

SSO errors appear in two places: on the Single Sign-On (SSO) page while setting up a connection, and on a Single Sign-On error page with Back to sign in during a sign-in. The tables below list the messages, their causes and the fixes.

Setup errors

Saving, testing or verifying a connection can return these messages:

MessageCause and fix
the OIDC issuer must be a public https:// URLThe issuer uses http, or a private or internal address. Use the identity provider's public https issuer.
issuer mismatch in discovery documentThe issuer entered differs from the issuer in the provider's discovery document. Copy the issuer value from the discovery document.
the JWKS endpoint returned no keysThe identity provider publishes no signing keys for this issuer. Check the authorization server.
that email domain is already used for SSO by another organizationAnother Multi-Router account has an SSO connection for the domain.
client secret is requiredA new connection needs the client secret.
We couldn't find the TXT record yet. DNS can take a few minutes to propagateThe DNS record is missing or not yet visible. Check its name and value, wait a few minutes, and verify again.
disconnect directory provisioning before changing SSO settingsUser provisioning is connected. Disconnect it to change the domain.
disconnect the directory before changing JIT or disabling SSOUser provisioning is connected. Disconnect it to change new-user access or turn the connection off.
disconnect directory provisioning before removing SSOUser provisioning is connected or set up. Turn it off to remove the connection.

Sign-in errors

A sign-in through SSO can stop on the Single Sign-On error page with these messages:

MessageCause and fix
No SSO is configured for that email domain.The email domain has no SSO connection, or the connection is turned off. Check the connection's email domain and toggle.
This organization hasn't verified ownership of its email domain yet.Verify the domain on the Single Sign-On (SSO) page.
SSO is not enabled for this organization.The connection was turned off during the sign-in. Turn it on in the card header.
Couldn't reach your identity provider.Multi-Router couldn't read the issuer's discovery document. Check the issuer and retry.
The identity provider rejected the sign-in.The client secret or redirect URI is wrong. Check the client secret, and that the app allows https://dashboard.multi-router.ai/sso/callback.
Sign-in could not be verified.The token's issuer or client ID differs from the connection, it has no email claim, it expired, or the identity provider reports the email as unverified.
Your identity provider signed you in with an email outside this organization's domain. If you are signed in to your identity provider as someone else, sign out there and try again.The identity provider session belongs to another account. Sign out at the identity provider and try again.
Your account isn't a member of this organization. Ask an admin to invite you.Invite-only is on and the person has no invitation, or the person is suspended or offboarded.
Your sign-in session expired. Please try again.The sign-in took more than 10 minutes. Start again.
Portal access is not configured for this organization.The person started at the Portal, and the organization has no Portal access for them. See Self-Service Provisioning.

Checklist

Most SSO problems come from one of these settings:

CheckWhere
The redirect URI is exactly https://dashboard.multi-router.ai/sso/callbackThe identity provider app
The issuer matches the discovery document, including /oauth2/default for OktaIssuer / Discovery URL
The issuer is copied exactly from the discovery document, with a trailing slash only when the document has oneIssuer / Discovery URL
The ID token includes the email claimThe identity provider app
The person is assigned to the appThe identity provider
The domain is verified and the connection is onThe Single Sign-On (SSO) page
The person has an invitation, when Invite-only is onPeople
Requiring SSOOverview
Was this helpful?