The following error scenarios might occur when you try out a SAML single sign-on (SSO) flow in identity provider (IdP) -initiated or service provider (SP)-initiated flows: 403 app_not_configured

If errors still occur, contact Google Cloud Support. Wait for a while and then try the flow again. To resolve any 500 errors for SAML app creation:

If the Service Provider Config service is unavailable a 500 error appears at the top of the screen when you click Finish.

While loading the schemas in NameID Mapping or Attribute Mapping, if the schema service times out or displays a backend exception, a 500 error appears at the top of the screen.

In the Google Identity Provider details section, if you click the Download Certificate or Download Metadata button when the certificates service backend service is unavailable, a 500 error appears at the top of the screen.

While creating a SAML app in the Admin console, you might see the following 500 errors: Use the already configured application or use a different entity ID. To resolve the 400 duplicate entity id error: You'll see this if you try to create an application with an already existing entity ID. While creating a SAML app in the Admin console, you might see the following 400 error: 400 duplicate entity id To aid in troubleshooting, use the SAML encode/decode tool to process a SAML request and response in human readable form from the HTTP Archive Format (HAR) file. Encode or decode SAML requests and responses

If you encounter any Security Assertion Markup Language (SAML) app error messages, here are some troubleshooting steps to help you.

Zoom sign in http 401 error