Okta Google Workspace Push Group Fails with Not Authorized Error
Last Updated:
Overview
A Google Workspace push group fails with an authorization error because the configured domain name is incorrect or the provisioning account lacks sufficient permissions. Verifying the domain name, enabling API access, and ensuring the provisioning account has Super admin permissions resolves the issue. Okta generates the following error:
Unable to update Group Push mapping target App group <xxx>: Failed to create group <xxx>. Not Authorized to access this resource/api
The following image displays the authorization error encountered during a Google Workspace group push.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Google Workspace
- Provisioning
- Group Push
Cause
This error occurs when the Google Workspace application contains an incorrect domain name configuration in Okta. The configured domain must match the domain used in the email address for Google authentication. Additionally, the error occurs if the provisioning account lacks Super admin permissions or if API access is disabled in Google Workspace.
Solution
How is the Google Workspace push group authorization error resolved?
Verify the Google Workspace domain configuration in the Okta Admin Console and ensure the Google provisioning account has the correct permissions and API access enabled.
- Verify that the Google administrator account used for provisioning has Super admin permissions in Google Workspace.
- Enable API access in Google Workspace by navigating to Security > API Reference > API Access and selecting Enable API Access.
- Verify that the account used for API access remains valid and active.
- Navigate to the General tab of the Google Workspace application in the Okta Admin Console and verify that the configured company domain matches the domain in the email address used for Google authentication.
