mirror of
https://github.com/J3vb/OwnCord.git
synced 2026-09-03 03:50:00 +03:00
* feat(auth): add revocable API tokens (bot/service auth) Add long-lived, revocable API tokens so headless clients (the introspection MCP tool, bots, CI) can authenticate without a password. Presented as "Authorization: Bearer <token>", a token authenticates as a specific user, inheriting that user's role and permissions. - migration 018 + dedicated api_tokens table (kept separate from sessions so bulk logout and the per-user session cap never touch these); only the SHA-256 hash is stored, raw token shown once at creation - auth.ResolveTokenHash: one shared bearer resolver that both AuthMiddleware and adminAuthMiddleware now call. Sessions are matched first so existing login behavior is unchanged; API tokens are a fallback only on session miss. A DB outage is returned wrapped, never mistaken for a bad token. - `server token create|list|revoke` CLI: mints directly against the DB with no HTTP and no login — the password-free bootstrap path - tests: resolver (8 cases incl. outage-not-fallthrough), db queries (6), api middleware integration (valid + revoked token) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(tools): add owncord-introspect MCP server A local MCP dev tool that lets Claude Code introspect a running OwnCord instance: read its logs, query any REST endpoint, and tail the desktop client's log file. It is a thin wrapper over the existing API plus the client log — no new product surface. - tools/mcp-introspect/index.mjs (Node/ESM, one dep: @modelcontextprotocol/sdk) exposes api_request (full read-write passthrough), server_logs (admin SSE ring-buffer stream), client_logs (reads the desktop log file) - authenticates with an API token (OWNCORD_API_TOKEN); pins the self-signed cert and skips hostname checks (the cert has no SAN) - registered in .mcp.json (secret-free ${OWNCORD_API_TOKEN}) - un-ignore tools/mcp-introspect/ so this shared dev tool is committed, while tools/livekit-server.exe and node_modules stay ignored - docs/mcp-introspect.md: how it works, tool reference, setup, troubleshooting Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(dependencies): update and add various crate versions in Cargo.lock * feat(admin): manage API tokens from the admin panel Add Owner-gated HTTP endpoints and a UI card to create, list, and revoke API tokens from the web admin panel. Previously only the `server token` CLI could manage them, which requires shell access to the host. - POST|GET|DELETE /admin/api/tokens in admin/handlers_tokens.go, wired in admin/api.go. All three are Owner-only (ownerOnlyMiddleware, like backups/updates): an HTTP token-mint endpoint is a network-reachable credential-minting surface, and API tokens deliberately survive password change + bulk logout, so a hijacked admin session must not mint one. - Reuses the same db.*APIToken calls as the CLI; create sources the actor from request context (audits who clicked, not the bound user); the raw token is returned once in the 201 body, never stored. - Add json tags to db.APITokenListItem for snake_case wire consistency. - Admin panel: "API Tokens" nav item + create modal, show-once reveal, revoke confirm in admin/static/index.html. - Tests: 7 in admin/api_test.go (+api_tokens table in the in-memory schema). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor: modernize to Go 1.26 idioms + enable modernize linter Apply `golangci-lint modernize` autofixes across the server and enable the linter in .golangci.yml so these stop re-accumulating (they built up only because modernize was never in the config). Production code: slices.Contains for hand-rolled membership loops (api router, ws origin, db/account, plugin manifest); strings.SplitSeq for allocation-free line/segment iteration (db/migrate, updater, livekit_proxy); strings.Cut (config); fmt.Appendf (dm_handler); min() (event_pruner); any (ws client). Tests: range-over-int, t.Context(), WaitGroup.Go, slices.Sort, maps.Copy, new(expr), interface{}->any. - plugin/manifest.go parent-traversal check applied by hand: modernize skipped it (two conflicting rewrites); used the slices.Contains form. - Removed the now-dead ptr() test helper after newexpr inlined its callers. - Dropped dangling sort imports left by the sort.Slice->slices.Sort rewrite. No behavior change. All four tag variants build, full test suite is green, and golangci-lint (with modernize enabled) reports 0 issues. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
48 lines
2.1 KiB
SQL
48 lines
2.1 KiB
SQL
-- name: CreateAPIToken :execresult
|
|
INSERT INTO api_tokens (user_id, token_hash, label, expires_at)
|
|
VALUES (?, ?, ?, ?);
|
|
|
|
-- name: GetActiveAPIToken :one
|
|
-- Auth-hot lookup: returns the token only if it is neither revoked nor expired,
|
|
-- so a resolved row is always usable. Matches the sessions never-expiring
|
|
-- convention (expires_at IS NULL).
|
|
SELECT id, user_id, token_hash, label, created_at, last_used_at, expires_at, revoked_at
|
|
FROM api_tokens
|
|
WHERE token_hash = ?
|
|
AND revoked_at IS NULL
|
|
AND (expires_at IS NULL OR strftime('%s', expires_at) > strftime('%s', 'now'));
|
|
|
|
-- name: ListAPITokens :many
|
|
-- Admin/CLI listing. Never selects token_hash (unrecoverable; only the raw
|
|
-- token shown at creation is usable).
|
|
SELECT t.id, t.user_id, COALESCE(u.username, '') AS username, t.label,
|
|
t.created_at, t.last_used_at, t.expires_at, t.revoked_at
|
|
FROM api_tokens t
|
|
LEFT JOIN users u ON u.id = t.user_id
|
|
ORDER BY t.id DESC
|
|
LIMIT 200;
|
|
|
|
-- name: RevokeAPIToken :execresult
|
|
UPDATE api_tokens SET revoked_at = datetime('now')
|
|
WHERE id = ? AND revoked_at IS NULL;
|
|
|
|
-- name: RevokeAPITokenByLabel :execresult
|
|
UPDATE api_tokens SET revoked_at = datetime('now')
|
|
WHERE label = ? AND revoked_at IS NULL;
|
|
|
|
-- name: TouchAPIToken :exec
|
|
UPDATE api_tokens SET last_used_at = datetime('now') WHERE token_hash = ?;
|
|
|
|
-- name: GetOwnerUser :one
|
|
-- The highest-privilege account (role with the greatest position), used as the
|
|
-- default identity for `token create`. FROM is users-only (role position is a
|
|
-- correlated subquery, not a join) so the row maps through userFromGen exactly
|
|
-- like GetUserByID, so keep this SELECT list identical to GetUserByID's.
|
|
-- A :one query already reads a single row via QueryRow, so no LIMIT is needed
|
|
-- (and an explicit LIMIT 1 is mis-emitted by sqlc here). ORDER BY puts the
|
|
-- highest-position role first, so that first row is the owner.
|
|
SELECT id, username, password, avatar, role_id, totp_secret, status,
|
|
created_at, last_seen, banned, ban_reason, ban_expires, identity_public_key
|
|
FROM users
|
|
ORDER BY (SELECT r.position FROM roles r WHERE r.id = users.role_id) DESC, id ASC;
|