Add local user accounts with first-run administrator setup #1555

Closed
opened 2026-10-27 13:40:52 +00:00 by sam · 0 comments
Owner

Dashboard access currently relies on shared credentials and chat messages lack a person identity. Add persistent local accounts, atomic first-admin setup, password sign-in, revocable sessions, account administration, and user-owned chat and memory while retaining SSO. Verify authorization, bootstrap races, session expiry and cross-user isolation.

Notes

First browser visit must set up organisation, initial workspace, canonical URL and first admin atomically. Then manage local accounts or OIDC in UI. Include passkeys for eligible secure origins. Apply OWASP Authentication and Authorization guidance; document every user-related authorization boundary and add allow/deny regression coverage, including cross-user and cross-org access.

Close reason

Implemented first-run org/workspace/admin setup, local accounts, revocable sessions, recovery, OIDC settings, passkeys and person-owned chat. Full task check passed. Disposable service/PostgreSQL checks verified bootstrap races, permissions, recovery and revocation; browser virtual authenticator verified passkey registration/sign-in. Authorization inventory and 112-route deny matrix included. Separate last-owner lifecycle issue remains tracked.


Imported from beads archie-core-rw3yp · GitHub #1699 · type feature · priority P1 · created 2026-10-15 · closed 2026-10-15

Dashboard access currently relies on shared credentials and chat messages lack a person identity. Add persistent local accounts, atomic first-admin setup, password sign-in, revocable sessions, account administration, and user-owned chat and memory while retaining SSO. Verify authorization, bootstrap races, session expiry and cross-user isolation. ### Notes First browser visit must set up organisation, initial workspace, canonical URL and first admin atomically. Then manage local accounts or OIDC in UI. Include passkeys for eligible secure origins. Apply OWASP Authentication and Authorization guidance; document every user-related authorization boundary and add allow/deny regression coverage, including cross-user and cross-org access. ### Close reason Implemented first-run org/workspace/admin setup, local accounts, revocable sessions, recovery, OIDC settings, passkeys and person-owned chat. Full task check passed. Disposable service/PostgreSQL checks verified bootstrap races, permissions, recovery and revocation; browser virtual authenticator verified passkey registration/sign-in. Authorization inventory and 112-route deny matrix included. Separate last-owner lifecycle issue remains tracked. --- _Imported from beads `archie-core-rw3yp` · GitHub #1699 · type feature · priority P1 · created 2026-10-15 · closed 2026-10-15_
sam added the highfeature labels 2026-10-27 13:40:52 +00:00
sam self-assigned this 2026-10-27 13:40:52 +00:00
sam closed this issue 2026-10-27 13:40:52 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1555