docs: record operator login rollout

2026-07-22 20:17:02 +02:00
parent 115f9850a7
commit 9db6cca2b1
1 changed files with 14 additions and 1 deletions
@@ -11243,4 +11243,17 @@ Pre-deployment validation:
  login with an HttpOnly/SameSite cookie, logout, signature tampering and the
  deployment guarantee that only a password hash reaches the container.
-Live deployment and login-journey evidence are appended after rollout.
+Live release evidence:
 - implementation commit `115f9850a703b3941b31d133e8547bf18ca37bff` was
  built as immutable AI image
  `geointel-all-in-one:115f9850a703b3941b31d133e8547bf18ca37bff-ai`;
 - the container became healthy, the live migration smoke passed against
  PostGIS 3.6 with Alembic head `202607160001`, and the frontend proxy returned
  the public session envelope while rejecting the protected projects endpoint;
 - a credentialed live journey on `http://192.168.10.150:1202` verified the
  complete boundary: signed out and blocked, successful login, authenticated
  project API access, successful logout, then blocked again;
 - Tower stores the operator credential only as a quoted PBKDF2-SHA256 hash plus
  an independent random signing secret. The plaintext password was not added to
  Git, documentation, the deployment template or the runtime environment.