Redact credentials from failed supplier requests
The HTTP client's error serializer includes Authorization headers and query parameters. A supplier timeout writes the outbound credential into a generic error log.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Log redaction · Error serialization · Secret hygiene
Estimated field mix
- Security80%
- Backend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional supplier integration signs incoming webhooks and uses an outbound API credential. Operators currently replace environment values by hand. Build with a deterministic secret-store adapter and fabricated keys only; no live provider account or production credential is part of the exercise.
Setup prerequisites
- Cryptographic hash APIs
- HTTP webhook handling
- Access control
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Log an allowlisted error projection with operation, status class, timeout, and correlation ID.
- Exclude headers, raw URLs, request bodies, and provider response bodies.
- Expose credential version identity only when it is a non-secret reference.
Implementation constraints
- Do not rely on replacing one known key value; future values and nested errors must remain safe.
Verification to include
- Diagnose a synthetic timeout through permitted metadata.
- Inject secret-like values into nested headers, URLs, and response bodies and assert absence.
Deliverables
- Safe supplier error serializer and redaction fixtures
Rollout and recovery
Replace error serialization before rotation drills; disable verbose client logging in the fixture configuration.
Value of the work
For the engineer: Practice credential lifecycle design, overlap windows, authenticated webhooks, and failure recovery without handling real secrets.
For the team: Review whether an engineer can make rotation auditable and fail closed while preserving availability and replay safety.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.