Security Patch: Updating google-github-actions to use Workload Identity Provider #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Security Patch: Updating google-github-actions to use Workload Identity Provider
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per Google's recommendation, the authentication method should be upgraded to Workload Identity Federation:
*Note: in addition to the code changes, the GCP account admin will need to follow these pre-requisite steps to configure Workload Identity Provider.
I learned about this potential security issue while working on an Aave DAO grant setting up the deployment scripts to write to multiple clouds. My testing ability for this was limited due to the permission restrictions on forked repos, but should be more straightforward for an Aave GCP account owner.