Skip to content

Capability Map

ChatLogin 0.2.1 adds truthful GET {prefix}/api discovery and AccountMenuUI role-aware host navigation; headless does not advertise pages. See New Service Onboarding.

Implemented Capabilities

Capability Status Boundary
Packaged demo Implemented (demo extra) chatlogin serve, four backend experiences, a template playground, and copyable integration examples; no production data
Managed-users preset 0.2.0 ManagedUsers, per-instance owner/admin/user, and default login/management/profile UI/API; explicit adoption only, with no old-store migration
npm frontend reuse Source package @chatarch/chatlogin 0.1.0 Framework-neutral TypeScript client and optional React login/account menu; shared protocol/CSS, Python authentication authority; see Frontend Integration; registry release is separate
ChatVoice legacy managed facade 0.2.0 Additive initialization over existing accounts / auth_sessions, one-time owner adoption, metadata-aware account matching, and managed-users CRUD; explicit consumer adoption required
Identity and authorization Implemented Principal, Role, 401/403, require_role, and require_owner; admin does not bypass ownership
Credential backends Implemented PasswordBackend supports one or more explicit accounts; CallbackBackend integrates host user stores; AsyncCallbackBackend awaits async upstream verification
ChatVoice compatibility backend Implemented (core, opt-in import) ChatVoiceAuth / ChatVoiceSessionStore; existing ChatVoice schema, fixed namespace and USER only; no schema migration or ChatVoice/web dependency
Legacy password verification Implemented verify_pbkdf2 verifies existing PBKDF2-HMAC-SHA256 salt/digest material without forced password migration
Sessions Implemented Opaque token, SHA-256-only storage, TTL, rotation, revocation, separate CSRF secret, and public purge_expired(); memory storage is demo/test-only
SQLite storage Implemented Public PrivateSQLite plus an instance-namespaced session store; POSIX uses a trusted 0700 directory and real-path mode=rw, rejects unsafe existing databases/sidecars, and does not present fd aliases as sidecar protection
FastAPI adapter Implemented (web extra) Configurable prefix, cookie, Origin/Host, body bound, rate limiting, JSON/headless routes, and dependencies
Default login UI Implemented (ui or web extra) ui installs only Jinja2; web also installs FastAPI/Starlette; wheel-packaged templates/CSS/JS
Web dependency compatibility gate Implemented web/dev declare starlette>=0.40,<2.0; compatibility tests cover Starlette 0.x, 1.3.1 and 1.6.0, and CI pins 0.x plus 1.3.x gates
Host template override Implemented Preferred template directories, block inheritance, whole-page renderer, and local custom stylesheet
ChatEnv namespace Implemented Keeps the ChatLogin typed profile without inventing an API key field

Integration Choices

  1. New site with application-managed accounts: explicitly adopt ManagedUsers + create_managed_auth, then let an operator bootstrap the first owner.
  2. New site whose accounts remain host-owned: start with default UI plus PasswordBackend or a host callback.
  3. Custom visual identity: keep the FastAPI adapter and replace template directories, template name, or renderer through LoginUI.
  4. Existing ChatVoice schema: select ChatVoiceAuth; to add user management on the same legacy schema, explicitly initialize ChatVoiceManagedStore and adopt one existing owner. Default UI, overrides and headless are all supported.

Backend selection: fixed/multiple accounts use PasswordBackend; sync host databases use CallbackBackend; async host databases use AsyncCallbackBackend; the ChatVoice schema uses ready-made ChatVoiceAuth. See the selection matrix.

Out of Scope

  • No standalone production login microservice, SSO, OAuth/email login, or MFA. Managed users provide instance-local account administration; fixed, callback, and ChatVoice adapter account management remains host-owned.
  • ChatLogin does not own meetings, files, cards, or other business data; hosts retain owner and policy decisions.
  • Guest is not a database account; guest experiences must be explicitly declared by the host.
  • No universal ORM or backend registry; the ChatVoice backend promotes our existing bridge with synthetic legacy-schema regression coverage.
  • Secrets, cookies, CSRF tokens, Authorization headers, and production credentials are never logged.

Multi-User Boundary

Account mappings, callbacks, the ChatVoice-compatible backend, and managed users support multiple identities. require_owner is a host-invoked ownership check, not automatic database row-level security; a managed owner does not bypass it. Different users require distinct stable user IDs. See Managed Users and the A/B lab and responsibility split.