Write a partner credential handling example for rotation and denial
Documentation encourages hardcoding keys and retrying every unauthorized response.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- SDK ergonomics · Documentation
Estimated field mix
- Developer tooling40%
- Security40%
- API design20%
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
- BAPIAUTH-106 · Revoke partner access across cached authorization decisions
- BAPIAUTH-107 · Rate-limit by delegated client without losing tenant-wide protection
- BAPIAUTH-108 · Expose an audit trail of privileged partner-client changes
- BAPIAUTH-109 · Design migration from broad keys to scoped delegated clients
Acceptance criteria
- Read credentials from the intended runtime boundary.
- Handle expiry and revocation without infinite retries.
- Show safe rotation using local test credentials.
Implementation constraints
- Examples must not log authorization headers.
Verification to include
- Run the example through a valid rotation.
- Revoke access and verify a terminal actionable error.
Deliverables
- Executable partner access guide.
Rollout and recovery
Version examples with the credential contract and remove obsolete broad-key guidance.
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.