> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/configuration/sso-configuration/troubleshooting.md).

# Troubleshooting SSO

Find SSO setup and sign-in errors, their common causes, and the checks your identity administrator or Silkline support can use to resolve them

Use the error code, the full message, and where the failure appears to choose the next check. A setup link configures the connection, and its setup page tests a real user sign-in through it.

Choose the section for your identity provider:

* [Microsoft Entra ID (Azure AD)](https://docs.silkline.ai/configuration/sso-configuration/azure-ad-oidc.md#troubleshooting)
* [Okta Workforce](https://docs.silkline.ai/configuration/sso-configuration/okta-workforce-enterprise.md#troubleshooting)
* [Google Workspace](https://docs.silkline.ai/configuration/sso-configuration/google-workspace.md#troubleshooting)
* [Other providers (generic OpenID Connect)](#other-providers-generic-openid-connect)

The shared sections below cover setup links, setup page test results, account/domain checks, browser sessions, verification, and the evidence to send support.

## Find the failing step

| Where it fails                                             | Start here                                                                             | Who usually acts                                                  |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| Settings cannot generate a link                            | SSO permission, verified domains, organization configuration                           | Your Silkline organization admin or Silkline support              |
| The setup link will not open                               | Missing, expired, used, or revoked link                                                | Whoever issued the link                                           |
| The setup form rejects a field                             | Issuer, client ID, secret Value, discovery response                                    | Your identity provider admin                                      |
| Microsoft, Okta, or Google displays an error               | Callback registration, tenant/cloud, app assignment, consent, sign-in policy           | Your identity provider admin                                      |
| The provider signs you in, but Silkline rejects the return | Email claim, verified domain, account/organization association, authentication session | Your identity provider admin and Silkline support                 |
| Silkline opens with the wrong account or organization      | Existing browser session and the organization selected                                 | The person signing in; support if reproducible in a fresh session |

## Setup links and form messages

Some messages below are shortened to their distinctive part. Copy the complete message when contacting support.

| Message or symptom                                                                                            | Common cause                                                                  | What to do                                                                                                                                                           |
| ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Unauthorized: createSsoSetupTicket requires all of: create_ssoConnection`                                    | The signed-in member does not have permission to create SSO connections.      | Ask an organization admin with SSO management permission to generate the link. Seeing the button does not establish permission to use it.                            |
| `Your organization has no verified SSO email domains`                                                         | No verified domains are available for this organization.                      | Ask Silkline support to register and verify the intended email domains.                                                                                              |
| `SSO settings are unavailable. Please try again later.`                                                       | SSO settings could not be loaded.                                             | Retry once. If it persists, send support the organization, timestamp, and message.                                                                                   |
| `SSO self-service is not available in this environment`                                                       | Self-service SSO is not configured for the environment.                       | Confirm the Silkline environment and contact support.                                                                                                                |
| `This setup link is missing its key`                                                                          | The URL was copied incompletely or its query string was removed.              | Open the complete original link. Do not build or edit its URL manually.                                                                                              |
| `This setup link has expired`                                                                                 | The link expired or its signed key is invalid.                                | Ask for a new link. The message does not establish that age was the cause.                                                                                           |
| `This setup link has already been used`                                                                       | **Done** was selected, or the link was revoked.                               | Check the active connection and outstanding links before generating another. This message alone does not prove setup completed.                                      |
| `The organization this link was issued for is no longer available`                                            | The organization is unavailable or disabled.                                  | Contact Silkline support. A new client secret will not resolve an organization problem.                                                                              |
| `Required`, `Enter the Client ID`, or `Enter the Client secret`                                               | A required field is empty.                                                    | Enter the values from the same IdP application.                                                                                                                      |
| `Must be a valid URL` or `Must be an https:// URL`                                                            | The issuer is malformed or uses HTTP.                                         | Enter the provider's public HTTPS issuer.                                                                                                                            |
| `Invalid client secret provided`                                                                              | The IdP explicitly rejected the submitted credentials.                        | Recheck that the client ID and secret belong to the same app. Copy the full secret Value, check expiry, and create a replacement secret if the value is unavailable. |
| `an SSO connection already exists for this organization`                                                      | The request conflicts with a connection already linked to the organization.   | Reopen a current setup link and review its replacement notice. Complete replacement only when that is intended.                                                      |
| `ticket domains are no longer verified`                                                                       | Domain verification changed after the link was issued.                        | Ask support to confirm the intended verified domains, then issue a current link.                                                                                     |
| `realm lacks the org-sso-first-broker-login flow` or `Silkline is not fully configured for this organization` | The authentication service or organization is missing required configuration. | Send the exact message to Silkline support. Changing IdP credentials does not repair this configuration.                                                             |

Explicit field or credential rejections during setup leave the link available for correction. Submitting again on the same link replaces the connection it created. A link ended with **Done**, or revoked, needs to be replaced.

## Setup page test results

After **Connect identity provider**, the setup page shows the outcome of each **Test sign-in**. Select **Fix the connection** to correct the credentials and submit again on the same link.

| Message on the setup page                                                                                                                      | What to fix                                                                                                                                                                   |
| ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `No sign-in reached Silkline. If your identity provider showed an error, fix the application there (redirect URI, assignment) and test again.` | The IdP stopped the sign-in before returning to Silkline. Read the error your IdP displayed, and check the redirect URI and the test account's assignment to the application. |
| `Silkline could not complete the exchange with your identity provider.`                                                                        | The IdP returned to Silkline but the token exchange failed. Re-check the client secret and the issuer, select **Fix the connection**, and test again.                         |
| `Your identity provider refused the sign-in (access_denied).`                                                                                  | Assign the test account (or its group) to the Silkline application in your IdP, then test again.                                                                              |
| `Your identity provider did not send an email address.`                                                                                        | Add the `email` claim or scope to the application. See your provider's guide for the email claim settings.                                                                    |
| `Signed in as ..., which is not a verified domain for ...`                                                                                     | The test account's email is outside the domains listed on the setup page. Test with an account on one of those domains, or ask support to verify the domain the IdP returns.  |
| `Silkline could not create or link the account.`                                                                                               | Contact support with the time of the attempt.                                                                                                                                 |
| `Your identity provider worked. Silkline could not finish the sign-in just now.`                                                               | The connection is working; Silkline's own sign-in step failed. Try again in a minute, and contact support with the time if it repeats.                                        |

## Microsoft Entra error codes

For setup validation, AADSTS codes, tenant/cloud selection, consent, and missing email claims, use [Microsoft Entra ID troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/azure-ad-oidc.md#troubleshooting).

## Okta errors

For assignment, client authentication, issuer selection, policy, and email claims, use [Okta Workforce troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/okta-workforce-enterprise.md#troubleshooting).

## Google errors

For OAuth client errors, callbacks, Workspace policy, account selection, and setup verification, use [Google Workspace troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/google-workspace.md#troubleshooting).

## Other providers (generic OpenID Connect)

Use the exact issuer from the selected authorization server, the client ID and secret from one confidential Web application, and the callback shown on the Silkline setup page. Check the provider's application assignment, consent and sign-in policy, and returned email before treating the connection as verified.

### Issuer and discovery errors

These checks also apply to Entra and Okta issuer discovery.

An issuer identifies an authorization server. Its discovery document is normally at `<issuer>/.well-known/openid-configuration`; enter the issuer itself in the setup form.

| Error text                                                                               | Check and common solution                                                                                                                                                    |
| ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `issuer discovery returned HTTP 400` or `HTTP 404`                                       | Check tenant ID, cloud, issuer path, and whether a metadata URL was pasted as the issuer. An unknown Entra tenant can produce HTTP 400.                                      |
| `issuer discovery returned HTTP 301` or another redirect                                 | Use the provider's canonical issuer that serves discovery directly. Discovery redirects are not followed.                                                                    |
| `issuer discovery returned HTTP 401` or `HTTP 403`                                       | The metadata endpoint requires authentication or is blocked. Ask the IdP admin to check public discovery availability.                                                       |
| `issuer discovery request failed` or a host-resolution error                             | Check DNS, public reachability, TLS certificate validity, and provider availability. Retry a transient outage; report persistent failures.                                   |
| `discovery document issuer does not match the submitted issuer`                          | Compare discovery's `issuer` with the submitted issuer. Use the same tenant and authorization server; Okta's organization issuer and `/oauth2/default` issuer are different. |
| `discovery document lacks authorizationUrl`, `tokenUrl`, or `jwksUrl`                    | The URL does not expose the required OIDC metadata. Ask the IdP admin for its OIDC discovery document.                                                                       |
| `issuer discovery document is not JSON` or `is too large`                                | A login page, proxy page, or incompatible metadata response was returned. Confirm the canonical public OIDC discovery endpoint.                                              |
| URL `must use https`, `must use the default https port`, or targets a non-public address | Self-service requires publicly resolvable HTTPS endpoints on port 443. Use the provider's supported public endpoints or ask support to review the integration.               |

## Errors after the provider returns to Silkline

A generic broker message such as `Failed to obtain token` needs the underlying provider error before choosing a fix. A secret error, cloud mismatch, policy denial, and an unavailable token endpoint require different remedies.

| Message or symptom                                                                           | Common cause and solution                                                                                                                                                                                                                                                                                  |
| -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `This sign-in method cannot be used for this email address`                                  | The provider returned no email, returned an email outside the connection's allowed domains, or the connection has no valid domain scope. Ask support to distinguish these causes. Check the source user's email and the actual returned email domain against the domains shown in Silkline SSO settings.   |
| `We couldn't reach Silkline to finish signing you in. Please try again.`                     | The final Silkline account sync could not reach the application service. Retry once; send support the timestamp if it continues.                                                                                                                                                                           |
| `Silkline is not fully configured for ...`                                                   | The selected organization lacks required identity-service mapping. Send the named organization and reference to Silkline support.                                                                                                                                                                          |
| `We couldn't finish signing you in ... quote this reference`                                 | The final account/organization sync failed. Send the reference and timestamp to support. Recreating an Entra app is not a general remedy.                                                                                                                                                                  |
| `Your access to this organization has been removed`                                          | The selected login path denies access to that organization. Ask an authorized organization admin or support to review the specific membership and login method.                                                                                                                                            |
| `Authentication session expired`, an expired code, or a missing login cookie                 | Start a fresh login from the Silkline application and finish it in the same browser. Avoid reusing an old callback, bookmarked provider authorization request, or back-button result.                                                                                                                      |
| A support log shows `CODE_TO_TOKEN_ERROR` with `pkce_verification_failed` or `Code mismatch` | The app's authorization-code exchange did not match its browser login attempt. Close unused sign-in tabs and start one fresh attempt. Overlapping attempts in the same browser can cause this failure. Report repeated failures to support; this code does not establish that the IdP secret is incorrect. |
| The page unexpectedly requests a password after SSO                                          | Confirm the selected account and the provider to which the browser was routed. Support should inspect account linking, credentials, and required actions; do not set a new password just to work around unexpected routing.                                                                                |
| The wrong account/organization opens, or a picker appears to reload                          | Check the account displayed on the login page. Use **Not you?** to change accounts, or start in a private window. Select the intended organization once. Report a repeatable failure with its timestamp and screenshot.                                                                                    |

The app can display `Something went wrong trying to log you in...` with a `Configuration` error after a failed callback. That is a general error, not a specific IdP diagnosis. Send support the timestamp so it can find the underlying error. Complete one login attempt at a time in the same browser context.

### Account and browser-session messages

| Message                                                         | Common solution                                                                                                                                                                                                   |
| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `We could not find an account for that email address`           | Confirm the email and Silkline environment. If this account should use SSO, ask support to check the domain routing, linked provider, and membership before changing client credentials.                          |
| `This Silkline account is deactivated`                          | Ask the authorized administrator or support to review the identity account's enabled state. An identity account being disabled differs from hiding an SSO member in Silkline.                                     |
| `Too many sign-in attempts`                                     | Wait for the indicated interval and follow the sign-in recovery guidance. Ask support about repeated lockouts; changing the SSO application is not a general remedy.                                              |
| `This sign-in link has expired` or `This page expired`          | Start a fresh sign-in from the app. A short-lived login link or authentication session is different from a seven-day SSO setup link.                                                                              |
| `Your browser didn't keep the sign-in cookie`                   | Complete sign-in in the same browser context. Check whether required sign-in cookies are blocked. Use a fresh private session to isolate stale state; report reproducible failures.                               |
| `You're already signed in`                                      | Open the Silkline application directly. Avoid replaying the provider callback or an already-completed login URL.                                                                                                  |
| `That sign-in link isn't valid` or `That request was not valid` | Start at the Silkline application rather than a saved authorization/callback URL. If it repeats, send the exact error and timestamp to support.                                                                   |
| `Silkline did not recognize that app`                           | Confirm the Silkline environment and start from its application URL. Support must inspect the application's identity-client configuration; this is not the same message as Entra rejecting an upstream Client ID. |
| An account-already-exists or account-linking prompt             | Ask support to inspect the expected SSO account-linking flow and existing identities. Preserve the existing user and membership records while resolving the conflict.                                             |

### The email claim is required

A successful provider sign-in must return an email on an allowed domain. A username that looks like an email does not establish that the provider returned an `email` claim.

See the provider-specific email and claim checks in [Microsoft Entra troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/azure-ad-oidc.md#email-claims), [Okta troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/okta-workforce-enterprise.md#troubleshooting), and [Google Workspace troubleshooting](https://docs.silkline.ai/configuration/sso-configuration/google-workspace.md#troubleshooting).

An alias, subdomain, or another company domain must be verified for the Silkline organization if that is the email the IdP returns.

## Verify the solution

1. Confirm the setup page shows a verified test sign-in, and Silkline's SSO settings show the intended connection and verified domains.
2. Open the Silkline application in a fresh private browser window.
3. Sign in with a real account assigned to the IdP application and on an allowed email domain. Complete required consent and MFA.
4. Confirm the browser returns to the Silkline dashboard with the intended account and organization.
5. If access must be revoked, follow your organization's IdP access policy. Hiding or archiving an SSO member in Silkline is not a substitute for removing their IdP access.

## What to send support

Send <support@silkline.ai> the error code and full message, time with timezone, affected account and organization, and the step where it failed. Include the provider tenant/cloud, application client ID, registered callback URI, and provider request/correlation ID when available. For an error containing a Silkline reference, include that reference.

If sharing the failed authorization URL, retain `client_id`, `redirect_uri`, `response_type`, and `scope`, but remove authorization codes, `state`, `nonce`, tokens, and session values. Use a screenshot of the error without credentials. Do not send client secrets, passwords, setup-link keys, tokens, or an unredacted HAR/network export in a support ticket.
