Automation V3: Allowlist Provar in Google Workspace for Gmail Connections
This article covers the Google Workspace admin configuration required before users can add a Gmail connection in Provar Automation using Web-based Authentication. It also explains how to resolve the “Access blocked” (Error 403: access_denied) message that appears when this configuration is missing.
Prerequisites
You are signed in at admin.google.com as a Super Admin (or an admin with the Security and App access control privileges).
You have Provar’s OAuth Client ID: 402965450570-1gdkvke38ucl1t21nj6f2gn82l9hcn08.apps.googleusercontent.com
Allowlist Provar and Mark It as Trusted
Step 1: In the Admin Console, go to Security → Access and data control → API controls.
Step 3: Click Add app → OAuth App Name Or Client ID.
Step 4: In the search box, paste Provar’s Client ID (402965450570-1gdkvke38ucl1t21nj6f2gn82l9hcn08.apps.googleusercontent.com) and click Search.
Note: Searching by Client ID is the precise method. It returns the exact app rather than name matches.
Step 5: Select the check box next to the returned Provar app, then click Select.
Step 6: Confirm the OAuth Client ID shown matches the one above, then click Select again.
Step 7: Choose the scope of the configuration. Select the organisational unit or group that contains the users who will run Provar, or apply the configuration to the whole organisation, then click Continue.
Step 8: On the access screen, set the app access to Trusted (“Can access all Google services”).
Note: Choosing “Limited” only grants a subset of services and may not include the https://mail.google.com/ scope Provar needs. Trusted is the correct choice here.
Step 9: Click Configure (or Continue → Finish) to save.
After Saving
Changes can take up to 24 hours to fully propagate, although they are often much faster.
Once propagated, users in the selected organisational unit or group can launch the Google connection authorisation in Provar Automation, complete the normal browser sign-in and consent once, and Provar stores the access and refresh tokens. No App Password is involved.
In the Admin Console, the Provar app appears in the Third-party app access list with the status Trusted.
In Provar Automation, clicking Authorise … on the connection completes the browser sign-in without the Error 403 message, and the Access Token, Refresh Token, and Expires fields populate.
Troubleshooting: Error 403: access_denied
When you click Authorise … on a Google Applications connection and sign in with your Google account, the browser may show the following message instead of the consent screen:
“Access blocked: Provar Test Automation has not completed the Google verification process. The app is currently being tested and can only be accessed by developer-approved testers. Error 403: access_denied”
Above: The Error 403: access_denied message shown during Google authorisation.
This means the Google account belongs to a Google Workspace organisation that has not allowlisted Provar as a trusted third-party app. Google blocks the OAuth sign-in until a Workspace admin completes the steps in the “Allowlist Provar and Mark It as Trusted” section above. The error can also appear if the configuration was saved recently and has not finished propagating.
If the error persists after propagation, confirm the user’s account is within the organisational unit or group selected in Step 7.
We use cookies to better understand how our website is used so we can tailor content for you. For more information about the different cookies we use please take a look at our Privacy Policy.
