You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm a bit unsure if this is a bug report, or a feature request.
In any case, for local testing of application code, we would like to impersonate the Service Account used for running the application on GCP.
It works when retrieving the ADC JSON with a user's own set of credentials, but not after adding --impersonate-service-account and then providing the application the JSON in either a well known location or via GOOGLE_APPLICATION_CREDENTIALS.
This results in "type": "impersonated_service_account":
Is your feature request related to a problem? Please describe.
I'm a bit unsure if this is a bug report, or a feature request.
In any case, for local testing of application code, we would like to impersonate the Service Account used for running the application on GCP.
It works when retrieving the ADC JSON with a user's own set of credentials, but not after adding
--impersonate-service-account
and then providing the application the JSON in either a well known location or viaGOOGLE_APPLICATION_CREDENTIALS
.This results in
"type": "impersonated_service_account"
:Describe the solution you'd like
Applications using this library should be able to authenticate with the impersonated Service Account.
Describe alternatives you've considered
Currently, local testing just uses the user's own credentials. Which may or may not have the same privileges as the Service Account.
Additional context
The text was updated successfully, but these errors were encountered: