2.3 KiB
ModelForge v1.2.3 — operator password sign-in
The console now opens with a Password field. A successful password exchange creates a signed, memory-only session lasting at most 15 minutes. Passwords are verified against a salted scrypt hash; the existing generated operator API key remains separate for signing and recovery.
Existing API-key clients remain compatible. Set MODELFORGE_OPERATOR_PASSWORD_HASH using
python scripts/operator_password.py, single-quote the hash in the Compose environment file,
and recreate the API. See installation. An unset hash preserves existing
API-key access. Password login fails closed when Redis is unavailable. Attempts are limited
across API processes, and forwarded headers do not change the peer used by the limiter.
These release notes describe the published hotfix built from v1.2.2. Database schema 20260830_0024, agent protocol 1, runtime
dependencies, model artifacts, capability bindings and promotion evidence are unchanged.
Upgrade classification: transparent. No model or inference runtime promotion is included.
Validation before release: targeted backend authorization, password and release-contract tests; frontend full test suite and production build; independent code review; isolated Redis 7 atomic parallel attempt, global limit and TTL checks. Deployment and exact-image acceptance must be recorded separately; source validation is not evidence of a successful production login.
Known limitations
Password login requires configured Redis and a password hash; there is no self-service password reset. Reloading the browser ends its session. Peers behind one reverse proxy share its attempt budget. Runtime and GPU qualification from v1.2.2 remains applicable only to unchanged exact runtime images; this hotfix does not qualify or promote new inference-worker images.
RC integration boundary
The development branch also incorporates this hotfix while retaining its newer schema
20260908_0028, named/managed identities and RC features. That source is not the published
schema-0024 hotfix image and is not qualified by its release evidence. Password sessions on the
RC branch pass the same identity, role and expiry checks as other operator sessions. Consult
the upgrade source boundary before deploying either build.