Skip to content

auth: log why a bearer is rejected - #6

Merged
reoring merged 2 commits into
mainfrom
auth-rejection-log
Nov 10, 2026
Merged

reoring merged 2 commits into
mainfrom
auth-rejection-log

Conversation

@reoring

@reoring reoring commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

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 of groups). 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.

@reoring
reoring marked this pull request as ready for review November 10, 2026 10:22
@reoring
reoring merged commit 7f9b073 into main Nov 10, 2026
3 checks passed
@reoring
reoring deleted the auth-rejection-log branch November 10, 2026 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant