Sandbox and certification flows
Goal
Validate an integration in non-production environments before promoting configuration to production tenants.
Prerequisites
- Sandbox tenant and partner rows distinct from production (synthetic ids only in examples).
- Certification checklist from your program office (external to this help).
Steps
- Exercise sign-in, partner launch, and read-only admin checks in sandbox with scoped actors.
- Capture evidence per compliance-evidence workflows when auditors require artifacts.
- Promote only after routing and federation summaries match approved baselines.
Verify
- Sandbox callbacks point to sandbox hosts; no production secrets appear in sandbox configs.
- Certification sign-off references agreement ids appropriate to your tier.
If it fails
Rollback sandbox changes, compare with golden routing rows, and open an incident if production impact is suspected.
Further reading
- Federation at the Tapestry boundary
- Compliance evidence console and monitoring runbooks (repository).