500 error when signing into GitLab.com with SAML

We are seeing report of users getting 500 errors when signing into their GitLab.com group with SAML SSO. We have identified the problem and reverted the change that introduce the error. We'll continue to monitor the problem. See more information in this issue: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/17672

We've identified the cause of the issue and are working on resolving it. While this affects a subset of SAML providers - the current workaround would be to temporary disable SAML until the issue is resolved. More details in gitlab.com/gitlab-com/gl-infra/production/-/issues/17672

We've identified the underlying issue and are working on resolving it. The expected time to resolution is about 4h from now. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/17672.

We are on track in terms of resolution. The fix should be present on GitLab.com within the next 3h. While this affects a subset of SAML providers (including Akamai MFA, Cisco Duo, Keycloak, NetIQ, PingOne MFA) one workaround is to temporary disable SAML authentication. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/issues/17672.