Table of contents
Is the handoff ready?
Use these checks before access expands or the first ticket begins.
Question
Ready: One observable token clock-skew handling outcome
Needs work: A request to inspect the whole system
Fixture
Ready: local issuer and verifier processes with controlled clocks and disposable keys
Needs work: Customer data or shared credentials
Evidence
Ready: issuer time, verifier time, claims, allowed skew, decision, error, and refresh result
Needs work: A pass label without observed values
Approval
Ready: Identity and security owners approve tolerance and token lifetime.
Needs work: The contractor changes production alone
Reproduce the token clock-skew handling failure safely
Services with different clocks can reject a fresh token or accept an expired one too long. Start with one case that can fail without touching customer records or production infrastructure. Write the expected result, stop condition, and reviewer beside the fixture.
Use local issuer and verifier processes with controlled clocks and disposable keys. Label every identity and artifact so a reviewer can distinguish test evidence from a live record.
Leave enough evidence for a second person
Capture issuer time, verifier time, claims, allowed skew, decision, error, and refresh result. Include the source revision and test time. If behavior changes between runs, retain both results.
Identity and security owners approve tolerance and token lifetime. A remote programmer can prepare the fixture, run bounded checks, and explain the result. New policy, privileged access, and release approval stay with the named owner.
Copy-ready brief
Put the operating agreement in writing.
Test one bounded token clock-skew handling case against written acceptance rules.
local issuer and verifier processes with controlled clocks and disposable keys
Record issuer time, verifier time, claims, allowed skew, decision, error, and refresh result.
Identity and security owners approve tolerance and token lifetime.
Frequently asked questions
What should the first run prove?
It should show the expected token clock-skew handling result for one controlled fixture.
What belongs in the handoff?
Include issuer time, verifier time, claims, allowed skew, decision, error, and refresh result, the source revision, and any untested condition.
Who approves a production change?
Identity and security owners approve tolerance and token lifetime.
Sources
- NIST Secure Software Development Framework
NIST guidance for managing software development risk.
- GitHub pull request reviews
First-party documentation for review and approval.
