grant/keysat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix stale scoped-API-key panel note in api_keys.rs doc comment

Browse Source
This commit is contained in:
Grant
2026-06-16 13:05:26 -05:00
parent b088bfc062
commit d2846ac6ae
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
licensing-service/src/api/api_keys.rs
+3 -4
View File
@@ -5,10 +5,9 @@
//! script a credential that does only what it needs to. Operator-friendly //! script a credential that does only what it needs to. Operator-friendly
//! flow: //! flow:
//! //!
//! 1. Operator mints a new key via `POST /v1/admin/api-keys`, picking a role //! 1. Operator mints a new key via the Settings → "Scoped API keys" panel
//! from a fixed list (Read-only / License issuer / Support / Full admin). //! in the admin SPA (or directly via `POST /v1/admin/api-keys`), picking a
//! (A clickable Settings → API keys panel in the admin SPA is planned; //! role from a fixed list (Read-only / License issuer / Support / Full admin).
//! until then keys are minted through the API.)
//! 2. The create response returns the raw token ONCE. The token never //! 2. The create response returns the raw token ONCE. The token never
//! appears in any response afterward — only its sha256 hash is stored. //! appears in any response afterward — only its sha256 hash is stored.
//! 3. Agent uses `Authorization: Bearer <token>` like the master key. Each //! 3. Agent uses `Authorization: Bearer <token>` like the master key. Each