Skip to main content

Google SSO: Troubleshooting

  • Updated

You receive a "Problem connecting to your SCM provider" or "Internal Server Error" error message when testing Google / Google SAML login / team sync

Cause:

OpenID Connect 

Legacy People API has not been used in the project before, or it is disabled.

Admin SDK API has not been used in the project before, or it is disabled.

SAML

Admin SDK API has not been used in the project before, or it is disabled.

Both

The admin email is not a user in the account or is the email of the service account

Solution:

OpenID Connect

    1. We are aware that newer projects cannot enable the Legacy People API.
    2. We are currently working on using the newer API.
    3. Contact support to enable SAML
    1. Enable the Admin SDK API for the project.
    2. Wait a few moments and try again.

SAML

    1. Enable the Admin SDK API for the project.
    2. Wait a few moments and try again.

Both

  1. Use an email address of a user.
  2. There is a note on https://developers.google.com/admin-sdk/directory/v1/guides/delegation that mentions:

    Only users with access to the Admin APIs can access the Admin SDK Directory API, therefore your service account needs to impersonate one of those users to access the Admin SDK Directory API. Additionally, the user must have logged in at least once and accepted the Google Workspace Terms of Service.

Related articles