Sandbox tenant environment
Advanced Identity Cloud add-on capability
Contact your Ping Identity representative if you want to add a sandbox environment to your PingOne Advanced Identity Cloud subscription. Learn more in Add-on capabilities. |
A sandbox tenant environment is a standalone environment separate from your group of development, staging, and production tenant environments. It tracks the rapid release channel, which lets you test the newest features and fixes from Ping Identity before they reach your other environments. It’s mutable like your development environment, but because changes can’t be promoted, you have more freedom to test various use cases. You can run experiments without worrying about accidentally promoting your changes to your upper environments.
For example, you can create user journeys and test them before deciding which one you’d like to use in your development environment. You can safely do this in a sandbox environment because nothing in that environment is part of the promotion process. This means you don’t need to worry about cleaning up unused user journeys.
Sandbox usage guidelines
There are some important guidelines to note when using a sandbox environment. In particular, the environment should not be used for load testing, and it should not contain personally identifiable information (PII):
Feature | Description | ||
---|---|---|---|
Production use |
No |
||
Static & dynamic configuration |
Mutable via the UI and REST APIs |
||
Configuration promotion |
No |
||
Max number of identity objects |
10,000 identity objects
|
||
Log retention |
1 day |
||
Monitored via Statuspage.io |
No |
||
SLA |
N/A (support provided at lowest priority level, see below) |
||
Personally identifiable information (PII) |
No |
||
Load testing |
No |
||
Level of support |
Business hours Monday–Friday (excluding public holidays in Australia, Singapore, France, United Kingdom, United States, and Canada) |