Tenant Environments

Overview

Each Identity Cloud tenant includes three separate environments that let you build, test, and deploy your IAM applications:

Tenant Environment Description

Development

Used for building and adding new features.
Limit the number of identities to 10,000.

Staging

Used for testing development changes, including testing applications under realistic settings such as stress tests and scalability tests.

Production

Used for deploying applications into operation for end users.

Identity Cloud also offers standalone sandbox environments.

Environment configuration

Identity Cloud uses a promotion model to move configuration changes through the three tenant environments.

The development environment is mutable. This means that you can easily make configuration changes to the environment, either through the browser UI or through the REST API.

By contrast, the staging and production environments are not mutable. This means that you cannot make configuration changes to these environments directly. Instead, the ForgeRock support team promotes the changes from the development environment. This is known as a configuration promotion and is done on a request basis by submitting a support ticket.

In situations where you want a configuration value (such as an authentication token) to be distinct in each environment, the ForgeRock support team can also set this up. This is known as a configuration intervention and is also done on a request basis by submitting a support ticket.

Tenant Environment Mutable Making Configuration Changes Setting Distinct Environmental Configuration Values

Development

Yes

UI or REST API

Configuration intervention request

Staging

No

Configuration promotion request

Production

No

Configuration promotion request