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
Workload identity accessing GoogleAPIs without having a static service account token. GKE metadata server available in each pod is used to fetch tokens.
Workload identity tokens work as a replacement for GSA token, they are not accepted by GSuite Admin API, because Admin API requires impersonalization for GSuite admin. Impersonalization IS possible with workload identity token, hence this proposal.
if google connector config specifies adminEmail, but does not specifies serviceAccountFilePath Google connector attempts to use workload identity token to impersonate GSuite Admin and create Admin API client instance
The text was updated successfully, but these errors were encountered:
Workload identity accessing GoogleAPIs without having a static service account token. GKE metadata server available in each pod is used to fetch tokens.
Workload identity tokens work as a replacement for GSA token, they are not accepted by GSuite Admin API, because Admin API requires impersonalization for GSuite admin. Impersonalization IS possible with workload identity token, hence this proposal.
Example use of GSuite admin impersonalization can be found here: https://github.com/salrashid123/oauth2#impersonated-credentials-with-domain-wide-delegation
So proposal is following:
adminEmail
, but does not specifiesserviceAccountFilePath
Google connector attempts to use workload identity token to impersonate GSuite Admin and create Admin API client instanceThe text was updated successfully, but these errors were encountered: