fix(auth): clarify admin login flow

Use admin-specific Telegram copy and define the missing credential API. Replace predictable bootstrap passwords with random one-time secrets.
2026-08-21 07:39:30 +04:00
parent 14d46ceaa6
commit 98c39f6844
8 changed files with 125 additions and 6 deletions
--- a/docs/backend/TRACK-S-SECURITY-RBAC-CONTRACT.md
+++ b/docs/backend/TRACK-S-SECURITY-RBAC-CONTRACT.md
@@ -96,7 +96,8 @@ Customer/seller PII is exposed only to roles that need it for their scope (e.g.
 Each marketplace ships with one bootstrap `MARKETPLACE_ADMIN` account, seeded at provisioning time (Phase 9 launch step):

 - `login` = marketplace slug (`projectName`)
- `password` = `{projectName}2026$`, flagged `mustChangePassword: true`
+- `password` = cryptographically random one-time secret delivered out of band,
+  flagged `mustChangePassword: true` (never derive it from the marketplace slug)
 - Login succeeds but every non-auth request 403s with `PASSWORD_CHANGE_REQUIRED` until password is changed.

 ```