Troubleshoot: Google Workspace Integration

Cause: The users do not have a secondary/additional form of MFA.

Resolution: Ensure users have a secondary/additional form of MFA, like Authenticator (TOTP) or 2-Step Phone verification phone.

Cause: When users are removed and the directory is added in the same save action, the group members are synced in the group's original state and then the removed users are updated to indicate they no longer have access.

Resolution: The change in membership and then adding the directory must be completed in two separate steps. Remove the user(s) and save the group. Then, add the directory and save the group again.

When using the Google Apps User Provisioning and Sync utility, administrators occasionally receive a 500 Error during the import process. This occurs after an admin has successfully established an OAuth connection and attempts to import users.

Cause:

The most prevalent cause of this is the Google Apps account itself not having API Access enabled under admin.google.com > Security > API Reference > API access.

Resolution:

We recommend that you enable the API access setting and re-attempt to import users. 

• If provisioning from JumpCloud to Google, the user might not show up in the Google Apps Admin Console.
• Previously provisioned users don’t synchronize new passwords when reset in JumpCloud.

Cause:
The username and/or password doesn't comply with Google's name and password guidelines. 

Resolution:
Make sure the Gmail username and password comply with Google's guidelines.

If the above resolutions don't solve the issue, contact your JumpCloud administrator to verify your account status and assist in troubleshooting. If signing up for service, please submit a support request and confirm the email address being used in the form.

Alternate Resolution:

Add JumpCloud as a Trusted Third-Party application.

When a new user is created in JumpCloud, their account is not synchronized to and does not appear in Google Workspace list of users. Existing users will synchronize without issue.

Cause:

The Google Workspace instance has run out of available license seats.

Resolution:

Increase the number of seats in your Google Workspace instance.

When you attempt to authorize the Google Workspace Directory integration using a Super Administrator account, you can receive an “Error 400: admin_policy_enforced” error message.

There are three common causes for the "Error 400: admin_policy_enforced" message:

Cause 1:

API Access is Restricted. 

To fix this and Enable API Access: 

1. Log in to the Google Workspace Admin Console.
2. Go to Security > API Controls > Manage Google Services
3. FindGoogle Workspace Admin and select Change Access
4. Select Unrestricted: Any user-approved app can access a service to enable API Access

Cause 2:

One of the systems is disabled.

To fix this and enable systems:  

1. Log in to the Google Workspace Admin Console.
2. Go to Security  > API Permissions.
3. Enable any disabled systems:

Cause 3:

URL Blocking is blocking necessary URLs like the GAM client_id.

To fix this and unblock necessary URLs:  

1. Log in to the Google Workspace Admin Console. 
2. Go to Devices > Chrome Settings > User Settings.
3. Confirm that necessary URLs aren’t blocked.

Cause: LastName is missing.

Resolution: Verify the user has a valid Last Name.

Ensure that Enable management of groups and memberships in Google Workspace is enabled. Once it is enabled, click Save. You should see the Distribution Group Email column.

Cause: There are pre-existing restrictions or security measures that prevent access

Resolution: Use the following steps to resolve this issue:

1. Navigate to the Google Workspace Admin dashboard.
2. In the top search bar, search for and select API Controls.
3. Under App access control, click MANAGE THIRD-PARTY APP ACCESS.
4. Search for the name “JumpCloud” or the matching ID and click Change Access.
5. Select Trusted and then click Continue.
6. Once this done, admins would be able to successfully add domain to Google Workspace in JumpCloud.