Let people sign up, be approved, and issue their own keys
CI / test (push) Successful in 1m9s

Every key needed an operator with a shell. This adds the login system that
made that necessary, which is the thing I argued against building until it was
asked for — so it is built as if it will be attacked, because a public login
form is.

Signing up produces an account that can do nothing. Approval is what makes it
work and stays on the CLI: having a shell on the control plane is what makes
someone an administrator, and that is a smaller thing to get right than roles
and an admin UI that mints credentials.

The details that matter:

Passwords are argon2id, where a slow hash is correct — the input is chosen by
a human and has a dictionary, which is the opposite of an API key. Both kinds
of authentication now live in this codebase and they are in separate packages
so neither set of assumptions leaks into the other. Length is the only rule:
composition rules push people towards Password1! and cost more entropy than
they buy.

Signup never says whether an address already has an account, and sign-in
answers the same way for a wrong password and a missing account — verifying
against a dummy hash when there is no user, so a stopwatch cannot enumerate
accounts. Account state is checked after the password, not before, so guessing
an address reveals nothing about it. Guessing is bounded per address rather
than per IP: an attacker has many addresses to come from and one to guess
against, and limiting by IP locks out an office behind one NAT.

Sessions are server-side, so signing out and suspending take effect
immediately rather than whenever a token expires; suspension is checked in the
same query that resolves the session, because a second round trip is a check
somebody eventually forgets. Every state-changing form carries a CSRF token
verified against a hash in the session — a cookie authenticates the browser,
not the page that asked.

Key ownership is enforced in the UPDATE rather than by reading first, so a
guessed key id from another account changes nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5 committed 2026-09-16 09:32:35 +02:00
1 parent 8d35faf6f8
commit 216fc9bb03
22 files changed
+2263 -39

No files matched your search

+82 -17
View File
@@ -3,18 +3,81 @@
Written for whoever operates an llmgw deployment: the person with a shell on the
control plane machine.
Everything here runs as the user the server runs as, so the files it creates stay
readable by it:
There are two ways a person gets a key. Pick one and put it in the config.
| | Self-service | Operator-issued |
|---|---|---|
| Config | `auth.signup_open: true` | `auth.signup_open: false` |
| They do | sign up, wait, then make their own keys | wait for a link |
| You do | approve once | issue every key |
| Good for | more than a handful of people | a few, or machines |
Self-service does not mean open. A signup produces an account that can do
nothing at all; **approval is what makes it work**, and approval needs a shell
here rather than a session cookie, because it is the step that decides who gets
to spend the cluster.
Everything below runs as the user the server runs as, so the files it creates
stay readable by it:
```
sudo -u llmgw llmgw keys <command> --store /var/lib/llmgw/llmgw.db
sudo -u llmgw llmgw <command> --store /var/lib/llmgw/llmgw.db
```
The `--store` flag is repeated in every example below. Set it once in a shell
alias if you do this often; it deliberately has no server-side default beyond
`/var/lib/llmgw/llmgw.db`.
## Self-service
## 1. Decide where the user belongs
Turn on the form:
```yaml
auth:
enabled: true
store: /var/lib/llmgw/llmgw.db
signup_open: true
```
The landing page then links to it, and the rest is:
```
llmgw users list --pending --store …
ID EMAIL NAME STATE PROJECT SIGNED UP
usr-k4mq… ayse@example.com Ayşe pending - 4m12s ago
llmgw users approve usr-k4mq… --project default --by ilker --store …
```
That is the whole operator loop. From then on they sign in at `/login`, and
`/profile` is where they create keys, see when each was last used, and revoke the
ones they are done with. A key is shown once on the page that creates it and
never again.
**This gateway sends no email.** There is no "your account was approved" message
and no password reset, so tell people what to expect: they sign up, they tell
you, you approve, they sign in. If that loop is too manual for your size, it is
the thing to automate — not the approval step.
To close an account:
```
llmgw users suspend usr-k4mq… --store …
```
which closes their sessions immediately. Their **API keys keep working** — those
are separate credentials, and revoking them is a separate step:
```
llmgw keys list --project default --store …
llmgw keys revoke key-… --store …
```
That separation is deliberate: a suspended person's running jobs should not all
fail at once without someone deciding they should.
## Operator-issued
With `signup_open: false` there is no form, and you issue keys yourself. This is
also the path for things that are not people — CI, a notebook server, a script.
### Decide where the key belongs
Keys hang off a project, projects off a team, teams off an organization. Limits
can be set at any of those levels and compose downward by taking the **most
@@ -33,7 +96,7 @@ live in whatever provisions the machine.
Split it when you want separate limits or separate reporting, not before.
## 2. Issue the key as a one-time link
### Issue the key as a one-time link
```
llmgw keys create --store … \
@@ -67,7 +130,7 @@ provisioning something that is not a person:
llmgw keys create --store … --project ci "github-runner" > /run/secrets/llmgw-key
```
## 3. Set limits
## Limits
Limits are optional. A key with none is unlimited, which is the right default on
a private cluster and the wrong one the moment the gateway faces anything else.
@@ -105,7 +168,7 @@ llmgw keys limits --store … --scope project --id default \
--budget 50000000 --period month # 50 units a month
```
## 4. Point people at the right place
## The landing page
Someone who reaches the gateway without a key sees the landing page. Tell it who
to send them to, or it can only shrug:
@@ -121,7 +184,7 @@ shown as text. Other schemes are never linked — configuration is not always
written by whoever runs the gateway, and a `javascript:` href on a page served to
every visitor is a short path to a stored XSS.
## 5. What the user does
## What the user sees
They open the link, press the button, and get the key once. The page shows them
the base URL and a working `curl`, and points at two endpoints:
@@ -132,7 +195,7 @@ the base URL and a working `curl`, and points at two endpoints:
`/me` is there so nobody has to ask you "why was I rate limited" or "how much
have I used". It is outside `/v1` because it is not part of the OpenAI API.
## 6. Afterwards
## Rotation and revocation
```
llmgw keys list --store … --project default
@@ -157,10 +220,12 @@ need revocation to bite faster.
## What this does not do
- **No self-service.** Every key needs someone with a shell here. That is
deliberate: an endpoint that mints credentials needs a login system, and this
project does not have one. If you outgrow it, that is the thing to build, not a
password field on the dashboard.
- **No SSO.** Same reason.
- **No email.** No approval notice, no password reset, no address verification.
Someone who forgets their password needs you, and there is no command for that
yet — `llmgw users create` is the workaround, which changes the address.
- **No SSO.** Accounts are local, with local passwords.
- **No roles.** Every approved account can do the same things: make its own keys
and nothing else. Administration is the CLI, and having a shell here is what
makes someone an administrator.
- **Rate limits are per gateway instance.** With two instances each counts its own,
so the effective limit doubles. v1 is single-instance by design.