Revoke partner access across cached authorization decisions
Revoked clients retain access until a long cache TTL expires.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Caching · Revocation
Estimated field mix
- Security70%
- Distributed systems30%
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 operations platform lets customers connect automation clients. Broad API keys and inconsistent tenant checks make delegated access difficult to review.
Setup prerequisites
- Create a local authorization service and synthetic partner clients for two organizations; generate disposable test credentials only.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BAPIAUTH-101 · Define partner scopes from concrete API operations
- BAPIAUTH-102 · Bind delegated credentials to organization and client identity
- BAPIAUTH-103 · Return non-enumerating errors for unauthorized partner resources
- BAPIAUTH-104 · Enforce authorization in nested and batch partner operations
- BAPIAUTH-105 · Rotate partner credentials without indefinite dual-key access
Acceptance criteria
- Bind caches to current authorization revision.
- Recheck or invalidate revoked authority within the declared bound.
- Deny new operations after revocation.
Implementation constraints
- Cached membership is not permanent authority.
Verification to include
- Serve a current authorized cache entry.
- Revoke the client and verify cached access stops within policy.
Deliverables
- Revocation-aware authorization cache.
Rollout and recovery
Prioritize denial when revision freshness is unavailable.
Value of the work
For the engineer: Practice delegated authorization, resource scoping, and secure public API ergonomics.
For the team: Provide usable partner access that remains least-privilege and revocable.
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.