mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 15:23:29 +00:00
Merge branch 'fix/step-up-and-session-revocation' into release/v1.39.3
# Conflicts: # messages/de.json # messages/en.json # messages/es.json # messages/fr.json # messages/it.json # messages/ko.json # messages/pl.json
This commit is contained in:
commit
03ccb21227
96 files changed
+3238
-495
No files matched your search
@@ -0,0 +1,9 @@
|
||||
-- When a browser session last re-proved a credential the account holds.
|
||||
--
|
||||
-- Exporting the whole record, making a share link, minting a token and the
|
||||
-- admin backup / reset / wipe actions now ask for a fresh proof, not just a
|
||||
-- live session. A second-factor proof keeps stamping `mfa_verified_at`, as it
|
||||
-- always has. A password proof on an account without a second factor stamps
|
||||
-- this column instead, so a password never satisfies a gate that asks for a
|
||||
-- second factor. Nullable, no default: a session that never re-proved has none.
|
||||
ALTER TABLE "sessions" ADD COLUMN "reproof_at" TIMESTAMP(3);
|
||||
@@ -1171,6 +1171,13 @@ model Session {
|
||||
// v1.23 — step-up freshness stamp. Set when the session completes a second
|
||||
// factor (or re-confirms it); `requireFreshMfa` (a later wave) reads it.
|
||||
mfaVerifiedAt DateTime? @map("mfa_verified_at")
|
||||
/// When this session last re-proved a credential through `POST
|
||||
/// /api/auth/reproof` (any method). Read by `requireRecentProof`, which on an
|
||||
/// account without a second factor accepts it as the fresh proof in front of
|
||||
/// exports, share links, token minting and the admin data actions. A
|
||||
/// second-factor proof also stamps `mfaVerifiedAt`; a password proof stamps
|
||||
/// only this, so it never satisfies a gate that asks for a second factor.
|
||||
reproofAt DateTime? @map("reproof_at")
|
||||
// v1.23 — sliding "last seen" for the user-facing active-session list.
|
||||
lastActiveAt DateTime? @map("last_active_at")
|
||||
|
||||
|
||||
Reference in new issue
Block a user