List the Tenant's keys
Every key of the Tenant by name, with its role (application, management or studio) and when it was issued. Keys themselves are never shown again.
managementKeyAuthorizationBearer <token>A management key of the Tenant (role management): it reaches the Management API (/v1/tenant/*) and /v1/me, as itself, never for a subject. Issued only on the Tenant's machine (nylorun-operate keys put <id> --role management) or from NYLORUN_MANAGEMENT_KEY_FILE. Never accepted from a browser (Origin).
Nylorun-Protocol*stringThe protocol version, 18
The keys, by id
application/json- response
keys*array<>import { createAdmin } from "@nylorun/admin";const admin = createAdmin();const keys = await admin.keys.list(); // never the keys themselves{ "keys": [ { "id": "string", "role": "string", "createdAt": "string" } ]}Record a Studio sign-in POST
Studio's server records that a browser signed in (`studio.signed_in`): on its loopback address, with a login token, or through a sign-in proxy (`forwarded`), and the person's subject when there is one. Only Studio's key (principal `studio`, derived from the admin key) may call it; any other management key is `403`.
Create or rotate an application key PUT
Issues a new application key named `keyId` and returns it this once. An application key of that name is replaced: the old one stops authenticating at once. A management key, `studio` and `bootstrap` are refused.