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.

Sign up for GitHub

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

Jump to bottom

Refine logging after token revocation failure #766

Closed
mp911de opened this issue Mar 20, 2023 · 0 comments
Closed

Refine logging after token revocation failure #766

mp911de opened this issue Mar 20, 2023 · 0 comments
Labels
type: enhancement A general enhancement
Milestone
2.3.3

Comments

@mp911de
Copy link
Member

mp911de commented Mar 20, 2023

Now that we have the token accessor in place, it makes sense to log the token accessor upon revocation failure. We no longer attempt revoking batch tokens so we can provide additional value here instead of logging internals.
@mp911de mp911de added the type: enhancement A general enhancement label Mar 20, 2023
@mp911de mp911de added this to the 2.3.3 milestone Mar 20, 2023
mp911de added a commit that referenced this issue Mar 20, 2023
@mp911de
Refine logging on revocation failures.
480a295 
We now log token accessors if a token revocation has failed.

Closes gh-766
mp911de added a commit that referenced this issue Mar 20, 2023
@mp911de
Refine logging on revocation failures.
4e794ed 
We now log token accessors if a token revocation has failed.

Closes gh-766
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
2.3.3
Development

No branches or pull requests
1 participant
@mp911de