Skip to content
Dashboard
Theme
Theme

Google Workspace fixes

Connection Doctor fix steps for Google Workspace.

View Markdown

Fix steps for failed Google Workspace tests and sign-ins. For setup, see the Google Workspace guides.

Connection Doctor shows these steps when a test or sign-in through Google Workspace fails. Codes without their own Google Workspace steps use the generic fixes. Values in braces are filled in with the connection’s own settings in the dashboard and portal.

The identity provider did not release the user’s email claim.

  1. Make sure the user’s Google account has an email address; the email scope is requested automatically.

See the oidc_email_missing error reference.

The identity provider returned an error to the sign-in callback instead of signing the user in (most often the user is not assigned to the application, or canceled).

  1. In the Google Admin console, open Security > Access and data control > API controls > Manage third-party app access and make sure the OAuth client is allowed for the user’s organizational unit; in the Google Cloud console, check that the OAuth consent screen allows the user (Internal, or the user is a test user).

See the oidc_idp_error error reference.

A personal Google or Microsoft account signed in, and this connection only accepts work accounts.

  1. Ask the user to sign in with their Google Workspace account (name@your-domain), not a personal gmail.com account.

See the oidc_personal_account_refused error reference.

The account signed in from a Google Workspace domain or Microsoft Entra tenant that is not the one this organization verified.

  1. In the Google Admin console, open Account > Domains > Manage domains and check that the user’s primary domain is the domain verified in this setup.

See the oidc_tenant_mismatch error reference.

The identity provider refused to exchange the sign-in code (often a wrong client secret or redirect URI).

  1. In the Google Cloud console, open APIs & Services > Credentials > the OAuth client and add {redirect_uri} to Authorized redirect URIs; check the client secret.

See the oidc_token_exchange_failed error reference.

The identity provider uses a different SP Entity ID (Audience) than this connection’s.

  1. In the Google Admin console, open the SAML app > Service provider details and set Entity ID to {sp_entity_id}.

See the saml_audience_mismatch error reference.

The identity provider sends the response to a different address than this connection’s.

  1. In the Google Admin console, open the SAML app > Service provider details and set ACS URL to {acs_url}.

See the saml_destination_mismatch error reference.

The response does not include the user’s email address.

  1. In the Google Admin console, open the SAML app > Attribute mapping and map Primary email to the app attribute email.

See the saml_email_missing error reference.

The identity provider refused the sign-in before sending an assertion.

  1. In the Google Admin console, open Apps > Web and mobile apps > the app > User access and turn it ON for the user’s organizational unit or group.

See the saml_idp_status_error error reference.

The response comes from a different identity provider (issuer) than the one configured here.

  1. In the Google Admin console, download the SAML app’s metadata and upload it here; the issuer is the “Entity ID” shown in Google identity provider details.

See the saml_issuer_mismatch error reference.

The response has no user identifier (NameID).

  1. In the Google Admin console, open the SAML app > Service provider details and set Name ID to Basic Information > Primary email.

See the saml_nameid_missing error reference.

The signature does not match the identity provider certificate we have on file (often after a certificate change).

  1. In the Google Admin console, open the SAML app > Download metadata (or the certificate) and upload it here.

See the saml_signature_invalid error reference.