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.
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
core: revoke the proper token on partial failures from token-related requests #7835
core: revoke the proper token on partial failures from token-related requests #7835
Changes from 1 commit
f59cb6a
bf17088
60ff5b9
0da7a49
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
we probably should log the error here as well?
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.
Perhaps failing here should produce a slightly different log message to make orphan revocation by ID distinct from revocation by client token lease. Something like
failed to clean up token lease - id not found
vsfailed to clean up token lease - not found
. Iferr
will be sufficiently unique and the logger in fact captures that output, then this isn't necessary.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.
Are you referring to the difference between using
te.ID
here andresp.Auth.ClientToken
above? The revoke orphan call here ultimately points to to the same thing (i.e. the token ID that we're trying to revoke) since theauth
that we pass into this func is fromresp.Auth
and we setauth.ClientToken = te.ID
up in L1208. The revocation is not by client token lease ID.The reason why we're able to use
te.ID
is because we instantiate a new instance ofte
within the func, and in all three revoke orphan cases we're now referencing the token ID that's being created instead of the request's client token.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.
Yes, I was indeed referring to
te.ID
vsresp.Auth.ClientToken
. If it's all the same value and call then the messaging is sensible. Thanks.