Hi,
I’m debugging a Google Drive Connector v2 connection using
OAuth 2.0 - JWT Bearer and Google Workspace Domain-Wide Delegation.
Environment:
- Google Drive Connector v2
- Region: europe-west3
- Authentication: OAuth 2.0 - JWT Bearer
- Service account: (PII Removed by Staff)
- JWT Subject: my@do.main
- DWD scope: https://www.googleapis.com/auth/drive
The important part is the following A/B test.
- Same connector
- Same service account
- Same JSON key
- Same Secret Manager secret
- Same Drive connector version
WITHOUT JWT Subject:
Connection = ACTIVE
WITH:
JWT Subject = my@do.main
the connection fails with:
OAUTH [30004] Failed to retrieve OAuth token information.
unauthorized_client:
Client is unauthorized to retrieve access tokens using this method,
or client not authorized for any of the scopes requested.
I independently tested the exact same service account and subject
outside of Integration Connectors using Google’s Python auth library:
scopes = ["https://www.googleapis.com/auth/drive"]
subject = "my@do.main"
The token request succeeds and returns an access token.
The Connector DEBUG log shows:
authscheme=OAuthJWT
oauthjwtcerttype=GOOGLEJSONBLOB
oauthjwtsubject=my@do.main
scope=''
and then the connector sends a JWT bearer request to:
https://www.googleapis.com/oauth2/v3/token
which returns 401 unauthorized_client.
So the key/DWD/service account itself appears to work, while
impersonation through the Drive Connector does not.
Questions:
- Is JWT Subject / Domain-Wide Delegation supported for the
Google Drive Connector v2? - Does the connector generate the required OAuth JWT scope claim
when JWT Subject is configured? - Is there a supported way to specify the JWT scope for this
authentication mode? - Could this be a bug in the Google Drive Connector v2 / underlying
provider implementation?
I can provide sanitized DEBUG logs and the exact connection
configuration if needed.

