Operations
Production integration checklist
Roll out enforcement with trusted context, bounded retries, durable event handling, and tenant-aware configuration.
On this page
Authentication & trust boundaries
- Keep BASTION_SECRET_KEY and BASTION_WEBHOOK_SECRET exclusively on servers.
- Use a stable external account identifier and server-validated order amount and payment identifier.
- Populate login_succeeded only after server credential validation.
- Forward browser telemetry explicitly; do not forward client-spoofed IP or HTTP header claims as authoritative context.
- Enforce action before payment or fulfillment, and stop approval on API errors.
Rollout & integration tests
- Verify origins and Content Security Policy for the deployed domains.
- Pin SDK revisions and test upgrades before rollout.
- Observe monitor-mode events and legitimate outcomes before enabling enforcement.
- Test all four actions and the outage path in your own application.
- Test exact retries, changed-body 409, expired tokens, quota exhaustion, and partial batch failures.
- Verify webhook signatures, tampered-body rejection, duplicate deliveries, and receiver downtime.
- For SAML, test an active member, a nonmember, certificate rotation, and an expired sign-in.
Operate safely
- Store request_id beside orders and durable webhook receipts.
- Make fulfillment and webhook side effects idempotent independently of scoring receipts.
- Monitor remaining quota, effective plan, and retention before depending on feature access.
- Synchronize receiver and identity-provider clocks.
- Coordinate key rotation with both backend and frontend releases.
- Keep a tested recovery path for legitimate customers blocked or held for review.