Files
OmniRoute/src/lib/db/migrations/100_cli_access_tokens.sql
Diego Rodrigues de Sa e Souza 3c9883bb73 Release v3.8.29 (#4126)
OmniRoute v3.8.29 — 115 commits since v3.8.28. Full CHANGELOG + 41 i18n mirrors. All content quality gates green (build, unit 8/8, vitest 188/188, PR test policy, quality gates extended, docs sync, quality ratchet). Remaining red CI checks are pre-existing release flakes (coverage-shard/integration/node-compat teardown), a new transitive undici advisory in electron devDeps, and a workflow-level CodeQL fail (0 open alerts). VPS-validated by the operator.
2026-06-19 06:49:01 -03:00

19 lines
844 B
SQL

-- CLI access tokens — scoped credentials for remote-mode management commands.
-- Distinct from `api_keys` (inference traffic): these authorize the `omniroute`
-- CLI / dashboard to run management operations against a (possibly remote) server.
-- Only the SHA-256 hash of the secret is stored; the plaintext is shown once at
-- creation. Scope is one of: 'read' | 'write' | 'admin' (admin ⊃ write ⊃ read).
CREATE TABLE IF NOT EXISTS cli_access_tokens (
id TEXT PRIMARY KEY,
token_hash TEXT NOT NULL UNIQUE,
token_prefix TEXT NOT NULL,
name TEXT NOT NULL,
scope TEXT NOT NULL DEFAULT 'read',
created_at TEXT NOT NULL DEFAULT (datetime('now')),
last_used_at TEXT,
expires_at TEXT,
revoked_at TEXT
);
CREATE INDEX IF NOT EXISTS idx_cli_access_tokens_hash ON cli_access_tokens(token_hash);