--- title: Adding environments description: Use the wizard to add PingFederate and PingAccess environments to PingCentral. component: pingcentral version: 1.14 page_id: pingcentral:pingcentral_for_iam_administrators:pingcentral_add_environments canonical_url: https://docs.pingidentity.com/pingcentral/2.2/pingcentral_for_iam_administrators/pingcentral_add_environments.html llms_txt: https://docs.pingidentity.com/pingcentral/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: October 30, 2023 superseded_by: https://docs.pingidentity.com/pingcentral/2.2/pingcentral_for_iam_administrators/pingcentral_add_environments.html section_ids: before-you-begin: Before you begin steps: Steps choose-from: Choose from: choose-from-2: Choose from: result: Result: --- # Adding environments Use the wizard to add PingFederate and PingAccess environments to PingCentral. ## Before you begin Ensure that PingFederate is configured as a token provider for PingAccess. For more information, see [Configuring PingFederate as a PingAccess token provider](pingcentral_configuring_pf_token_provider.html). ## Steps 1. On the **Environments** page, click **Add Environment**. 2. On the **Connect to Instances** page, connect to a PingFederate or PingAccess environment: ### Choose from: * To connect to a PingFederate environment, complete the **PingFederate Admin**, **PingFederate Admin Username**, and **PingFederate Admin Password** fields with your authentication information. * To connect to a PingAccess environment, complete the **PingAccess Admin**, **PingAccess Admin Username**, and **PingAccess Admin Password** fields with your authentication information. | | | | - | --------------------------------------------------------------------------------------------------- | | | If an environment is disabled or offline, you will be unable to add the environment to PingCentral. | If this is the first time that you have set up this environment, and the initial validation fails, you see a **Skip Verification** option. If you select this option, it allows you to skip the validation process. However, if you set it up correctly, you won't see this option. If the environment is disabled or offline, and you edit the connection configuration, the **Skip Verification** check box is automatically marked. 3. Click **Next**. 4. On the **Name Environment** page, complete the **Name**, **Short Code**, and **Description** fields. 5. **Optional:** To configure whether non-administrators need approval for promoting an application to an environment, select an option from the **Approval Type** list: ### Choose from: * Select **No Approval** to allow non-administrators to promote applications to the environment freely. * Select **Approval Required** to indicate that application promotion requires approval. * Select **Require Approval If Any Expression Fails** and proceed to the next step to configure an **Approval Expression**. * Select **Require Approval If Any Expression Succeeds** and proceed to the next step to configure an **Approval Expression**. 6. **Optional:** If you selected **Require Approval If Any Expression Fails** or **Require Approval If Any Expression Succeeds**, you must configure a Spring Expression Language (SpEL) expression in the **Approval Expression** field. You can use SpEL expressions to determine whether an application requires approval or not. For more information, go to [Creating and testing approval expressions](pingcentral_create_test_expressions.html) on this page. | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | For more information on SpEL, see [Spring Expression Language (SpEL)](https://docs.spring.io/spring-framework/docs/3.0.x/reference/expressions.html) in the Spring Framework documentation. | 7. **Optional:** To enforce random secret generation and restrict non-administrators from creating their own, select the **Enforce Random Client Secrets** check box. PingCentral will generate random client secrets. 8. **Optional:** To add an identity provider (IdP) *(tooltip: \
\

A service that manages identity information and provides authentication services to relying clients or SPs within a federated or distributed network.\

\
)* certificate, select the appropriate certificate in the **Signing Certificate** list or to upload your own certificate, click **Choose** and enter the certificate password in the appropriate field. Click **Save and Close**. ### Result: The environment is displayed on the **Environments** page. If you chose to protect the environment, you see a shield icon next to its name. Depending on the type of environment, you also see a **PF** or **PA** icon. The color of this icon represents the status of the environment. A green icon indicates that the environment is verified while a red icon indicates that the environment isn't verified. Depending on if an environment is online, offline, or disabled, you see the environment status in a display bar. You also see the toggle switch that you can click to disable the environment and indicate that it is undergoing maintenance. 9. Click **Save and Continue**. 10. Click the expandable icon associated with the environment to view environment details. ![A screen capture showing the Environments page, which lists all of the environments and displays details regarding each environment when the associated expandable icon is clicked.](_images/val1695410125951.png) Environment details include: * A link to PingFederate. * A link to PingAccess. * A description of the environment. * The total number of applications hosted on this environment and a breakdown of OAuth *(tooltip: \
\

A standard framework that enables an application (OAuth client) to obtain access tokens from an OAuth authorization server for the purpose of retrieving protected resources on a resource server.\

\
)* or OpenID Connect (OIDC) *(tooltip: \
\

An authentication protocol built on top of OAuth that authenticates users and enables clients (relying parties) of all types to request and receive information about authenticated sessions and users. OIDC is extensible, allowing clients to use optional features such as encryption of identity data, discovery of OpenID Providers (OAuth authorization servers), and session management.\

\
)* clients, Security Assertion Markup Language (SAML) *(tooltip: \
\

A standard, XML-based, message-exchange framework enabling the secure transmittal of authentication tokens and other user attributes across domains.\

\
)* service provider (SP) *(tooltip: \
\

In SAML, an entity that receives and accepts an authentication assertion issued by an IdP, typically for the purpose of allowing access to a protected resource.\

\
)* connections, and PingAccess applications. Click these links to access filtered lists of these applications on the **Applications** page. | | | | - | -------------------------------------------------------------------------------------------------------------- | | | If an environment is unavailable, applications in that environment don't display on the **Applications** page. |