Z User 41af78e628 fix(auth): re-issue JWT after password change so session_version bump does not lock users out ...

After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.
fix(auth): re-issue JWT after password change so session_version bump does not lock users out
After change-password the DB session_version was incremented while the browser
kept the old token, so every API returned 401 and the UI bounced back to login.
Also route first-login to /change-password and surface API error messages.

2026-09-08 15:50:19 +00:00

..

api.go

fix(auth): re-issue JWT after password change so session_version bump does not lock users out

2026-09-08 15:50:19 +00:00

bcrypt_test.go

fix: align listener generation with mihomo official spec

2026-08-16 09:21:42 +08:00

bcrypt.go

fix: align listener generation with mihomo official spec

2026-08-16 09:21:42 +08:00

jwt_test.go

test: cover case-insensitive Bearer parsing

2026-08-18 13:48:49 +08:00

jwt.go

fix(auth): repair JWT source and validate claims

2026-08-29 15:09:43 +08:00

service.go

feat(distribution): add complete installation and recovery workflows

2026-09-08 22:47:35 +08:00