auth: add clock-skew leeway to JWT expiry validation #523
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/thwap-pagesd#523
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
internal/auth/auth.gousesjwt.WithLeeway(0). Valid Authentik tokens that expire within the leeway window of the daemon's clock are rejected under even small client/server clock skew.Context: PR #521 (
internal/auth/auth.go:88).Suggested fix: use a small leeway (e.g. 30s–60s) via
jwt.WithLeeway(time.Second * 30).