Repository navigation
auth: log why a bearer is rejected - #6
Merged
Merged
Conversation
…ata, never the token)
reoring
marked this pull request as ready for review
November 10, 2026 10:22
reoring
force-pushed
the
auth-rejection-log
branch
from
November 10, 2026 10:22
4fcf6b2 to
0459512
Compare
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
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.
Follow-up to the 2026-11-10 Craftsman report: one user's browser got repeated 401s from the API for a bounded period and nothing recorded why (the server logged no requests).
On a 401 the server now writes one
tracker auth rejected:line with method, path,X-Request-Id, a reason category and unverified token metadata (alg, kid, iss, aud, azp, iat, nbf, exp, JSON type ofgroups). Never the token, signature, subject, email or group values (table-tested).Not released: no tag. Merge and tag (0.1.8) after the demo.
Not in this PR: the SPA's re-auth on 401 only navigates to
/and reuses the rejected edge session.