Harden Codex auth redaction policy #129
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Issue #117 identifies
bot_bottle/codex_auth.pyas a remaining security-sensitive hotspot. Its dummy auth generation and redaction behavior depend on schema knowledge and heuristics. Future Codexauth.jsonfields could accidentally survive redaction if they do not match the current token/secret/key naming patterns.Desired outcome
Add a PRD for making Codex auth redaction policy explicit and coverage-driven. The PRD should cover allowlist vs denylist behavior, nested JWT/auth claim handling, regression fixtures, and failure behavior for unknown sensitive-looking fields.
Parent context
Carved out from the broader hotspot review in #117.