This guide lists the most frequent SAML SSO error messages and their possible solutions.
If you are a member of a SAML SSO-enforced Workspace and you experience any errors related to SAML SSO, we recommend that you first contact your Workspace owner so that the owner can check your SAML SSO status.
For Workspace owners, we recommend checking out our SAML SSO guide.
no-saml-sso-identity; There is no SAML SSO identity for this user.
You might be receiving this error because you are not a SAML SSO group member. As the first steps of troubleshooting, we advise you to contact the Workspace owner to see if you have been added to the SAML SSO group of the SAML SSO provider. The Workspace owner has to check if the email address associated with your SAML SSO is the same as the one that’s been used in Bitrise when you were invited to the Workspace.
saml-wrong-account-url; There's no connected SSO for this email address. You are either logged in to Bitrise with another account or the connected SSO for this account is not valid anymore.
We recommend that you check with the Workspace owner if the email address associated with your SAML SSO is the same as the one that’s been used in Bitrise when you were invited to the Workspace.
enable-sso-login; You have to be logged in the first time you authorize your organization to log you in with SSO. Please log in with your original credentials first and then visit the SSO login URL.
It seems you have not authorized your organization (Workspace) to let you log in via SSO to the Workspace. We recommend you log in to Bitrise using your credentials first, open the link you got in your letsconnect@bitrise.io invitation email in a separate tab, and follow the instructions. For more information, check out our SAML SSO guide.