-
Notifications
You must be signed in to change notification settings - Fork 101
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 Federation #233
Comments
This is possibly a dupe of #171, but I couldn't tell for sure. |
Currently we only support AWS for workload identity federation. I have not yet investigated the details of how to work with github actions, but referring to the Go source, the credential source should be either FILE, URL, or Executable in this case. I will check what the credential source will actually be. |
I've run into the same issue and am currently investigating it. {"type":"external_account","audience":"//iam.googleapis.com/***","subject_token_type":"urn:ietf:params:oauth:token-type:jwt","token_url":"https://sts.googleapis.com/v1/token","credential_source":{"url":"***","headers":{"Authorization":"***"},"format":{"type":"json","subject_token_field_name":"value"}},"service_account_impersonation_url":"https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/***:generateAccessToken"} As far as I've investigated the URL type implementation in Go, it does not seem to be that complicated: |
I see this was merged a couple of weeks ago. Any chance you'll publish a new release with it soon? |
@theoribeiro Now I published google-cloud-auth v0.13.2 |
Unfortunately I'm still getting |
Ah, never mind! This is behind a feature gate that I didn't know. I added |
Hi, I have GitHub Action CI workloads which authenticate to GCP using 'Workload Identity Federation through a Service Account' following the configuration in the linked google-authored action.
I have enabled the
external-account
feature ingoogle-cloud-auth
.When using
google-cloud-storage
in this CI environment authentication fails withError: external account error : Unsupported Subject Token Source
.I believe this is expected behavior based on a TODO in the codebase: https://github.com/yoshidan/google-cloud-rust/blob/main/foundation/auth/src/token_source/external_account_source/mod.rs#L107-L108, but I wanted to file an issue to track progress and see if there are any workarounds, particularly in a GitHub Actions environment.
The text was updated successfully, but these errors were encountered: