Sign-in failed or expired
SSO sign-in failed or expired. Try again or contact your administrator. is a general error. It can indicate a rejected identity or account as well as an expired sign-in transaction. Start again from your company’s saved sign-in link or Forecastable’s Single sign-on button. The button asks for your existing account’s work email; the company link goes directly to your provider. Finish authentication in the same browser session and avoid reopening an old callback URL. If the provider accepted your login but Forecastable rejected the return, check these items:Authentik returns false for email verification
Authentik 2025.10 and later default toemail_verified=false. Under Company-managed identities, this is accepted when all organization, domain, provider, and existing-account checks pass.
Under Verified email, configure real email verification or a trusted existing verification process and map its result. Do not mark emails true merely to suppress the error. See Identity trust policies and Authentik’s guide.
Company sign-in link is unavailable
Ask your administrator to copy the current saved link from Settings > Single sign-on > Company sign-in link. Check that you are using the correct environment. A renamed address stops working, and a disconnected provider, deleted organization, or organization with no verified domains cannot start SSO through the link. If Create link or Save address reports that the address is taken, choose another name. Previously used addresses remain reserved to their original organization. Reserved authentication names are also unavailable. If the link reaches your provider but fails after returning, use the sign-in checks above. The provider’s authenticated email must belong to the selected organization and an exact verified domain. Company-managed identities still require an existing active account. A company link does not bypass identity policy or create access.DNS verification fails
- Check that you used a TXT record, the displayed host, and the entire displayed value.
- Avoid duplicating the domain when your DNS provider automatically appends it.
- Wait for public DNS propagation, then click Verify again.
- Generate a new record if the challenge expired or was regenerated. The previous value is no longer valid.
- A domain already assigned to another organization needs an ownership review; it cannot be claimed from this page.
Issuer or callback errors
The OIDC issuer identifies your provider. The redirect URI identifies Forecastable’s federation callback. Copy the issuer from your provider’s discovery document and copy the redirect URI from the Forecastable settings page. Preserve exact paths and trailing slashes. For OIDC, register the Cognito callback ending in/oauth2/idpresponse. For SAML, register the ACS URL ending in /saml2/idpresponse and the exact displayed audience. Production and development may have different callback hostnames. A custom Forecastable authentication domain must be provisioned before it can replace the existing Cognito hostname.
Do not use Google sign-in’s /login/google/return callback for enterprise SSO.
Settings check succeeds, but login fails
Check settings verifies AWS configuration. It cannot prove that your provider authenticates a real user, sends the expected fields, or assigns that user to the application. Use Test sign-in with an eligible account before requiring SSO. An existing provider’s saved secret is not displayed. An empty secret input after loading does not mean the deployed secret is missing. If credentials need rotation, enter the new value and apply the connection, then test a fresh login.Password or Google sign-in stops working
When Require single sign-on is on, ordinary users must use the organization’s provider. Google is blocked even for backup accounts. Explicit backup accounts can use native password sign-in and password reset. If SSO is unavailable, use a tested backup password account to turn off required SSO. If no backup works, contact a platform operator. Do not delete identity links, move accounts between organizations, or remove native sign-in from the shared Cognito client to resolve the incident.SSO succeeds, but access is missing
SSO authenticates the user; it does not assign organization roles or synchronize directory groups. Check Forecastable membership and permissions. A verified-email pending user needs explicit access approval. Company-managed users must already have an account in the organization.Information for support
Provide the environment, approximate failure time with timezone, work email, selected trust policy, provider protocol, and whether the error appeared before or after the provider login. Support can correlateauth.sso.denied and other authentication audit events.
Never share client secrets, passwords, authorization codes, tokens, SAML assertions, or an unredacted callback URL. The general error and historical audit event may not identify the precise failing stage; provider attributes and account/domain configuration help narrow the cause.