login.html/login.js: the two reset views are gone along with the reset-token
handling, and the sign-in form now says which password to type - "your Windows
password, the same one you use to sign in to your computer" - using the .hint
class the page already had, so no new CSS and no new literal.
"Forgot password?" is KEPT and points at https://primecontrols.okta.com/. An
earlier draft of this task deleted the link and I proposed a plain "contact IT"
sentence instead; Okta is the better answer, and with no app password and no
break-glass it is the only recovery path that exists.
Three details that would each have broken it:
- The old click handler on #forgot-link called preventDefault() to swap views.
Left in place it would have silently swallowed the navigation, so the link
would look right and do nothing. There is now deliberately no handler, and
login.js says why so nobody adds one back.
- target="_blank" without rel="noopener noreferrer" hands the opened page a
window.opener handle back to the login page.
- Worth recording since it was checked rather than assumed: the CSP allows
this. form-action 'self' governs form submission, not link navigation, and no
navigate-to directive is set - so a plain <a href> off-origin is fine and the
nginx config needs no change.
login.js also handles 503 distinctly now. T10.2 made that mean "the directory
is unreachable or misconfigured", which is our fault - showing "invalid
password" would send people hunting for a password they no longer have while a
deploy is broken.
Also removed, because T10.3 deleted the endpoints behind them and leaving them
would have produced visible 404s rather than dead-but-harmless markup:
auth-guard.js the whole change-password dialog (POST /api/auth/password)
wp-sidenav.js the "Password / Change your password" menu entry that opened it
users.js the per-row "Reset password" action
users.js the password field in the create-account form - NewUserIn no
users.html longer accepts one, so the form was posting a rejected field
The self-row placeholder button pointed at a top-bar Password link that no
longer exists; it is now a plain "you" marker.
Verified: node --check passes on all four touched JS files; the only password
references left in html/ are the sign-in form and the SMTP config in admin.js,
which is unrelated and stays.
Logged BL-027 rather than acted on: the Okta URL is the first sign of an Okta
tenant on this estate, which means an OIDC flow is available in principle and
would remove the domain-lockout hazard that forced AUTH_MAX_ATTEMPTS to 2. D13
was decided and reaffirmed and T10.1-T10.4 are built, so swapping the mechanism
mid-wave is the reordering CLAUDE.md forbids. Recording is not reopening.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Cody Schaefer
ab7bce9f5b
