Start with test login: it shows every claim that arrived
and, per value, whether it mapped. The tables below are keyed on the exact text
you will see, so you can search this page for it.
| What you see |
Provider |
What to change |
AADSTS50011 |
Entra ID |
Register the sign-in redirect URI exactly, under Single-page application. |
cross-origin token redemption is permitted only for the 'Single-Page Application' client-type |
Entra ID |
The redirect URI is under Web; move it to Single-page application. |
AADSTS50105 |
Entra ID |
Assign the person (or their group) in Enterprise apps → Users and groups. |
AADSTS65001 |
Entra ID |
Consent missing for access_as_user; set Who can consent to Admins and users or grant admin consent. |
Error 400: redirect_uri_mismatch |
Google |
Add the sign-in redirect URI, with its trailing /, to Authorized redirect URIs. |
Error 403: org_internal |
Google |
The account is outside your Workspace; use a Workspace account. |
The 'redirect_uri' parameter must be a Login redirect URI in the client app settings |
Okta |
Add the sign-in redirect URI, with its trailing /, to Sign-in redirect URIs. |
User is not assigned to the client application |
Okta |
Assign the person or a group on the app’s Assignments tab. |
One or more scopes are not configured for the authorization server resource |
Okta |
A custom authorization server without a groups scope; use the plain Okta domain or add the scope. |
Callback URL mismatch |
Auth0 |
Add the sign-in redirect URI to Allowed Callback URLs. |
Invalid parameter: redirect_uri |
Keycloak |
Add the sign-in redirect URI to the client’s Valid redirect URIs. |
| What you see |
What it means and what to change |
The browser could not call the provider's token endpoint (...) |
The provider refuses browser requests from Seylo’s origin. Okta: Security → API → Trusted Origins with CORS. Keycloak: the client’s Web origins. Auth0: Allowed Web Origins and Allowed Origins (CORS). |
The token exchange failed (HTTP 400): invalid_request client_secret is missing |
Google: the client secret is not saved in Seylo, so the sign-in was redeemed in the browser without it, and Google refused. Paste the client secret into the provider and select Save provider; Seylo then completes Google sign-ins on its server with it. See the client secret. |
The provider refused the sign-in (<host>, HTTP <status>): ... |
A provider with a client secret saved refused the code when Seylo redeemed it on its server. The provider’s own reason follows the colon, with the secret cut out. Start the sign-in again; if it repeats, run the Test tab. |
Seylo could not reach the provider's token endpoint (<host>): ... |
Seylo’s server could not complete the request to the provider. Try again; if it repeats, run the Test tab. |
The identity provider refused the sign-in: ... |
The provider’s own reason follows the colon; look it up in the table above. |
A sign-in response arrived but this tab has no record of starting one. |
The sign-in was started in another tab, or the tab was reloaded mid-way. Start again from the sign-in screen. |
| What you see |
What it means and what to change |
No tenant is registered for token issuer "..." |
The provider signs with a different issuer than the one saved. Compare iss in the report with the issuer shown after Check the provider. For Entra, an issuer starting https://sts.windows.net/ means requestedAccessTokenVersion is not 2 in the app’s Manifest. |
Token validation failed: unexpected "aud" claim value |
The token was issued to a different client. Check the Client ID (Entra: Application (client) ID). The report prints both sides. |
This token carries no "hd" claim |
Google: a personal Gmail account. Only Workspace accounts can sign in. |
No tenant is registered for issuer "..." with hd="..." |
Google: an account from a different Workspace domain than the one saved. |
The configured role claim "..." is NOT PRESENT in this token |
The provider does not send the role claim, or under another name. Keycloak: Add to ID token on the realm roles mapper. Okta: the groups claim on the app’s Sign On tab. Auth0: the post-login Action. |
FINAL: none - every action will be refused |
Signed in, but no role mapped. Add the values the report lists to the Role map, set a Base role, or give the person a role on the Users tab. |
Token validation failed: "exp" claim timestamp check failed |
The pasted token has expired; get a fresh one. |
These are the page refusing a value before saving; each names what to enter.
| What you see |
What to enter instead |
"common" is a shared Microsoft endpoint, not your directory. |
Your Directory (tenant) ID from the app registration’s Overview page. |
That is the Secret ID, not the secret. |
The Value column of the client secret. If it is hidden, create a new secret. |
"..." is not an Application (client) ID. |
The GUID labelled Application (client) ID on the Overview page. |
Enter the domain only (acme.example), not an email address. |
Google: your Workspace domain. |
... does not end in /realms/<realm name>. |
Keycloak: the realm URL, e.g. https://sso.acme.example/realms/acme. |
Press "Check the provider" first. |
Seylo reads your provider’s configuration and shows it before saving. |
The SAML entityID "local://..." is reserved (or The OIDC issuer ..., or break-glass://...) |
The entity ID or issuer your identity provider publishes in its metadata. Values starting local:// or break-glass:// are written by Seylo itself and never come from a provider. |
The OIDC issuer "..." cannot be registered by an organisation: Seylo's own operators sign in through it. (or The SAML entityID ...) |
Seylo’s own staff sign in through that identity provider. If your organisation really uses it too, ask through Help → Contact support. |
You changed the provider details after checking. |
Press Check the provider again. |
"..." is not a Seylo role. |
One of viewer, releaser, approver, admin. |
The full code list, with fixes, is on the SAML page.
The three most common: signature-invalid (sign both the response and the
assertion), weak-signature-algorithm (SHA-1 - switch to SHA-256) and
no-in-response-to (the sign-in started from an app tile; point it at Seylo’s
Sign-on URL).