Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -44,8 +44,28 @@ does NOT run the strength policy. Enforcing 12-char + class requirements
there would lock out every user with a pre-policy password instead of
prompting them to rotate. The plain "is the field a non-empty 4+ char
string" presence-check in `UserValidationUtils.validatePassword` is what
guards the login form. The dashboard-banner soft-check from the detail-MD
is a follow-up.
guards the login form.
## Soft-banner (dashboard nudge)
The dashboard-banner soft-check is shipped: login runs the policy in
non-throwing mode against the submitted plaintext and stores a
`passwordPolicyOutdated` session flag. The tenant layout
(`apps/web/app/routes/app.$tenant.tsx`) combines that flag with the
`pwPolicyRemindAfter` snooze cookie via
`apps/web/app/services/auth/password-policy-banner.server.ts` and renders
`PasswordPolicyBanner` when the policy is not met.
The "Remind me in 7 days" button POSTs to
`/auth/password-policy-remind`
(`apps/web/app/routes/auth.password-policy-remind.tsx`), which sets the
snooze cookie for 7 days. The route intentionally lives under `/auth/*`
(a `publicWebRoutePrefixes` entry): the host-routing runtime
(`server/host-routing-runtime.ts`, `isRemovedLegacyRoute`) rejects every
other `/api/*` path on the tenant app host with 404, so an `/api/...`
resource route would be unreachable from the banner. The snooze is a pure
UX cookie per browser — deliberately not persisted in the database and
not a security control.
## HIBP fail-open