AI Implementation feature(821): First-Start Create Admin Modal (#2)
This commit was merged in pull request #2.
This commit is contained in:
+11
-4
@@ -3,7 +3,7 @@ type: database
|
||||
title: User Table
|
||||
description: The `user` table — accounts, roles, and statuses.
|
||||
tags: [database, user, auth]
|
||||
timestamp: 2026-07-21T14:18:00Z
|
||||
timestamp: 2026-07-21T14:43:00Z
|
||||
---
|
||||
|
||||
# Schema
|
||||
@@ -34,9 +34,16 @@ timestamp: 2026-07-21T14:18:00Z
|
||||
|
||||
# First-admin bootstrap
|
||||
|
||||
When the `user` table is empty of admins, `POST /api/v1/auth/register-first-admin`
|
||||
is the only endpoint that can create one. After that, the endpoint
|
||||
returns `409 SYSTEM_INITIALIZED`.
|
||||
When the `user` table is empty of admins, the dedicated
|
||||
`POST /api/v1/setup/create-admin` endpoint (see
|
||||
[Setup Endpoint](/api/setup.md)) creates the very first admin and
|
||||
auto-issues a session. Once any admin row exists the endpoint becomes
|
||||
inert and returns `404 NOT_FOUND`, so the route is effectively hidden
|
||||
in production.
|
||||
|
||||
The legacy `POST /api/v1/auth/register-first-admin` route is preserved
|
||||
for compatibility but the canonical first-admin flow now lives in the
|
||||
`SetupModule`.
|
||||
|
||||
# See also
|
||||
|
||||
|
||||
Reference in New Issue
Block a user