docs(auth): document optional authentication setup
- Explain opt-in configuration, protected surfaces, migrations and cookie behavior. - Document operator CLI, MCP bearer use, cleanup, and supported local origins.
This commit is contained in:
1 parent
d4d9bceb98
commit
9bdba32a34
5 files changed
+59
-2
No files matched your search
@@ -12,6 +12,8 @@ docker compose up -d --build
|
||||
|
||||
No configuration is needed: every setting has a default. To override one, copy `.env.example` to `.env` and uncomment it.
|
||||
|
||||
Authentication is **disabled by default**. To enable operator-managed accounts, set `AUTH_ENABLED=true` and provide a private `AUTH_JWT_SECRET`; then rebuild/restart the service and provision an account with the CLI. See [operator authentication](docs/development.md#operator-account-commands) for setup and browser/API usage. Existing deployments remain unauthenticated until explicitly enabled.
|
||||
|
||||
Everything is served from one container at **http://localhost:13000**: the UI at `/`, the REST API at `/api/v1`, MCP at `/mcp`, Swagger at `/docs`. Data is kept in `./data/`.
|
||||
|
||||
To see it work, import and run the [self-test example](examples/self-test/): a scenario that tests liqa itself using an environment, a credential and snippets.
|
||||
|
||||
Reference in new issue
Block a user