API keys act only as their account, and security changes revoke them
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
A request made with an API key no longer gets administrator access to timelines: the access checks (store.mjs access, liveState and comparison sources) match administrators through adminId, which is none while a key's request runs (key-requests.mjs). An administrator's own sessions are unchanged. Every security change now revokes the account's API keys with its other sessions (AccountSecurity.endAccess): turning two-factor authentication on or off, replacing recovery codes, adding or removing a passkey and confirming an email change, as password changes and resets already did. The notices, confirmations, OpenAPI descriptions and docs say so. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/2857419f37c24f81a45c4ba6fe188459167cb053
Open API keys act only as their account, and security changes revoke them in the timeline