github atom36942/atom v16.9.0
Atom 16.9.0

56 minutes ago
  • API keys: scripts and other systems call the API with Authorization: ApiKey atk_... instead of a password login. A key is an opaque random string (not a JWT) owned by the user who created it, stored only as its sha256 in the new table api_key, and resolved in the middleware to the owner's request.state.user (cached per worker for config_api_key_cache_sec, 60 s), so role, permission and ownership checks work unchanged. A route accepts keys only with "is_api_key": True in its config_api entry (none by default); a key may be limited to scopes (paths) and expire_days. New routes /my/api-key-create, /my/api-key-read, /my/api-key-delete, /admin/api-key-delete; new settings config_api_key_max (20 keys per user) and config_api_key_cache_sec. An unknown or expired key, or a deleted or deactivated owner, is 401 (docs/auth.md).

Don't miss a new atom release

NewReleases is sending notifications on new releases.