Define expected service names and certificate usage
A certificate signed by the internal CA is accepted for any service name.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- TLS fundamentals
Estimated field mix
- Security70%
- Networking30%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List expected subject alternative names per peer.
- Declare client and server usage requirements.
- Separate trust-chain validity from service identity.
Implementation constraints
- Use reserved local names and test certificates.
Verification to include
- Match the intended service identity.
- Reject a valid-chain certificate for another service.
Deliverables
- TLS identity contract.
Rollout and recovery
Review identities before enabling peer authentication.
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.