01What to validate in the sandbox
The first goal is not production certification. It is making sure the application and business process are shaped correctly before production credentials and certificates create additional dependencies.
Teams can validate request creation, cross-device and same-device journeys, status handling, webhook behaviour, policy selection and error states while keeping test activity isolated from production.
- Relying-party and tenant routing
- Verification policy selection
- QR and same-device entry points
- Backend status and callback handling
- Failure, expiry and cancellation flows
Why a platform sandbox is different
A vertical SaaS vendor is not testing one relying party. It is testing whether one integration can safely route requests for many customer organisations without mixing configuration or results.
Adminyra's sandbox is being built around the same multi-tenant objects as production—organisations, relying parties, applications and policies—so the integration shape does not need to be redesigned later.
Move to production deliberately
Test certificates and reference environments are not substitutes for production trust. Production activation will be a separate step with the appropriate relying-party registration, certificate material and verifier controls.
The public Adminyra API keeps the environment distinction explicit so developers cannot accidentally treat a successful sandbox transaction as a production identity verification.