Rehearse leaf renewal under an unchanged trust anchor
Routine renewal should not require every client to restart simultaneously.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Certificate operations
Estimated field mix
- Security50%
- Networking30%
- Site reliability20%
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 internal report exporter uses mutual TLS. Certificates are renewed manually, and operators cannot distinguish peer identity failures from network outages.
Setup prerequisites
- Generate disposable test-only certificate authorities and leaf certificates for loopback services; use no production keys.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BMTLS-101 · Define expected service names and certificate usage
- BMTLS-102 · Validate certificate chains without disabling hostname checks
- BMTLS-103 · Separate certificate expiry alerts from connection failure rates
- BMTLS-104 · Refresh connection pools after client-certificate rotation
- BMTLS-105 · Keep TLS errors from exposing peer secrets or request payloads
Acceptance criteria
- Issue a new leaf with the same declared identity.
- Overlap old and new leaves within policy.
- Verify old-leaf retirement after draining.
Implementation constraints
- Generated keys remain local temporary test assets.
Verification to include
- Renew without interrupting the declared local request flow.
- Reject the expired prior leaf after overlap.
Deliverables
- Leaf renewal rehearsal.
Rollout and recovery
Renew before expiry and retain a bounded rollback window.
Value of the work
For the engineer: Practice transport identity, trust-store changes, and certificate failure diagnosis.
For the team: Provide repeatable rotation and recovery behavior for authenticated service communication.
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.