-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(auth): avoid redundant executable run and preserve impersonated email in PluggableAuthCredentials #14446
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
Open
lsirac
wants to merge
8
commits into
main
Choose a base branch
from
fix/pluggable-auth-redundant-executable
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4d4f171
fix(auth): avoid redundant executable run and preserve impersonated e…
lsirac 93408f3
fix(auth): address adversarial review findings in PluggableAuthCreden…
lsirac 6969400
refactor(auth): simplify getImpersonatedCredentials and impersonated …
lsirac 4c6c1b9
refactor(auth): capture impersonatedServiceAccountEmail in PluggableA…
lsirac c120b58
refactor(auth): remove volatile and keep impersonatedServiceAccountEm…
lsirac 0d3b623
refactor(auth): revert ExternalAccountCredentials changes and call bu…
lsirac ad298c9
refactor(auth): guard impersonated refresh with getServiceAccountImpe…
lsirac 857be0a
refactor(auth): resolve impersonatedServiceAccountEmail once in Plugg…
lsirac File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I believe that falling back to
builder.impersonatedServiceAccountEmailwhenevergetServiceAccountEmail() == nullmeans that an external caller doingcreds.toBuilder().setServiceAccountImpersonationUrl(null).build()retainsthe stale
impersonatedServiceAccountEmailand still sendsGOOGLE_EXTERNAL_ACCOUNT_IMPERSONATED_EMAILinretrieveSubjectToken().Perhaps we want to address this at the same time as b/563846018 since it is very similar in nature? We'd just to make sure we also take care of resetting
impersonatedServiceAccountEmailas well.