mirror of
https://github.com/navidrome/navidrome.git
synced 2026-10-11 20:07:11 +02:00
d1b876097f
API v1 no longer mints short-lived JWT access tokens. Clients send the grant secret from POST /auth/login or /auth/setup as `Authorization: Bearer` on every request. Every request already looked the grant up in the database, so the JWT gave no speed or revocation benefit and only added a refresh loop, which early client authors pushed back on. The grant already is an API key: one per client sign-in, scoped and revocable. Revocation is now immediate on every node; the contract promises "within one minute". Removed: POST /auth/token, the grantAuth scheme, the TokenRequest and AccessToken schemas, the token_expired problem code, the API v1 JWT signer and its signing key, the grant liveness cache, and PropertyRepository.PutIfAbsent. ResolveGrant is now Authenticate. Short-lived tokens return later only as narrow media tokens for ?access_token= on media URLs, together with the media endpoints. Signed-off-by: Deluan <deluan@navidrome.org>
10 lines
368 B
YAML
10 lines
368 B
YAML
type: object
|
|
description: |
|
|
Capability modules this server implements, keyed by module. Keys are optional; a missing key means the
|
|
module is not implemented. New modules are added as new optional keys. These are server facts, not what
|
|
the calling grant may use.
|
|
properties:
|
|
core:
|
|
$ref: ./CoreCapability.yaml
|
|
password:
|
|
$ref: ./PasswordCapability.yaml
|