Look up an exact message shown on a WeaSSO page, what it means, and what to do next.
This page lists the errors, warnings, and confirmations that WeaSSO pages show today. Match the exact text on your screen. Where you see {...} or angle brackets, the page shows a real name or ID.
Check for typos and use the login name your organization gave you
User is locked
Too many failed verification attempts locked the account
Contact SSOSupport Bot to unlock it. Do not keep retrying
User is not active
An administrator deactivated the account
Contact SSOSupport Bot about the account status
User is no member of the required organization
The account exists but is not in the organization this app requires
Contact SSOSupport Bot to confirm which organization the account should belong to
GHE now uses CC SSO instead of Okta for sign-in. Your CC account has not been created yet. Please email ssohelp@chative.com with the subject “Request CC Account for GHE” from <your email>. We’ll help you set it up.
Your email is on the temporary GHE migration list, but the CC account is not ready
Send the requested email from the address shown in the message
Retry; after repeated failures, select Try another way
Passkeys are not supported in this environment. Please try another way to verify.
The current browser or device cannot complete verification
Switch devices or methods
WebAuthN is not supported by your browser. Please ensure it is up to date or use a different one (e.g. Chrome, Safari, Firefox)
The browser lacks the required Passkey capability
Update it, or use the latest Chrome, Safari, or Firefox
Registration failed. It looks like your device does not support Passkeys.
This device cannot register a Passkey
Use a device with a screen lock, fingerprint reader, or face unlock
Registration failed. Please retry, create a new challenge or choose a different method.
The registration request failed or expired
Refresh and start registration again
(Incompatible)
This device cannot use the Passkeys option
Switch devices or verification methods
Warning: Without a Authentication method enrolled. You will be required to ask for an OTP from your administrator to sign in to your account next time.
You are skipping Passkey setup
Contact SSOSupport Bot for a new OTP before your next sign-in
Face verification failed. Please ensure good lighting and face the camera directly, then retry.
The scan could not verify your face
Adjust the light and position, then select Re-verify
Camera requires an HTTPS secure connection.
The page was not opened from a secure address
Start again from your organization’s official HTTPS address
Face detection failed to load. Check your network and refresh.
The face-detection component did not load
Check the connection and reload
No face detected. Please face the camera.
The camera cannot see a face
Center your face and look at the camera
Camera: <browser error>
The browser could not use the camera
Check camera permission and whether another app is using it, then retry
The page does not show a different message for multiple faces, poor lighting, a failed liveness check, or a problem with the comparison service. All of these produce the general failure message above.