Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support workload identity in Google connector #1756

Closed
redbaron opened this issue Jul 3, 2020 · 1 comment · Fixed by #2530
Closed

Support workload identity in Google connector #1756

redbaron opened this issue Jul 3, 2020 · 1 comment · Fixed by #2530

Comments

@redbaron
Copy link

redbaron commented Jul 3, 2020

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:

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants