mirror of
https://tangled.org/evan.jarrett.net/at-container-registry
synced 2026-08-29 20:27:16 +00:00
A read-only app password authenticates fine via createSession but cannot call com.atproto.server.getServiceAuth, which is privileged — the PDS answers 403 InsufficientScope. That fell through to the generic non-200 path and became a 503, which invites the client to retry a request that can never succeed, with no indication of what is actually wrong. Classify it with a sentinel error and map it to a 403 at /auth/token, carrying text that names the fix: use a full-access app password. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>