Question
IN
Last activity: 2 Oct 2025 22:38 EDT
Pega Deployment Manager - Candidate system is not able to establish connection with Orchestrator.
I am getting the bellow error :
Orchestrator to Bravo
Bravo environment was not able to connect to the orchestrator. The 'Requires Authentication' checkbox is not selected in the api service package.
1.If you are not on Pega Cloud, ensure OrchestratorURL dynamic system setting is correctly configured on Staging.
2.Ports are correctly configured on the orchestrator.
3.DMAgentUser Operator is enabled on the orchestrator.
If you are using oAuth2.0 for communication,
1. Verify if the client credential is updated on DMReleaseAdmin_OAuth2 authentication profile.
2. Verify if the access token endpoint URL is correct in DMReleaseAdmin_OAuth2 authentication profile. Make sure that the 'Requires Authentication' checkbox is selected in the api package on the Staging environment.
Steps I have performed:
1.Perform "Revoke Access Token" option for the Operators across all the environments
2. Enabled the Option "Use Refresh Token if available" across the DMReleaseAdmin Auth Profiles
3. Regenerated the client secret from Orchestrator and update the same across all other candid environments
Also is there any alternative solution for "The 'Requires Authentication' checkbox is not selected in the api service package".
Even if i check this authentication box. I still get the Bravo environment was not able to connect to the orchestrator. error.
Updated: 1 Oct 2025 12:27 EDT
Pegasystems Inc.
GB
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a known issue with a documented solution. I recommend following the steps detailed below to resolve the problem with the 'Requires Authentication' checkbox and the connection error between the Bravo environment and the orchestrator.
Analysis
The error message "Bravo environment was not able to connect to the orchestrator. The 'Requires Authentication' checkbox is not selected in the api service package" indicates that the authentication settings in the API service package are not correctly configured. This issue is consistent with several documented cases where the 'Requires Authentication' checkbox was not enabled, leading to connection failures between environments.
Proposed Solution
To resolve this issue, please follow these steps:
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
This is a known issue with a documented solution. I recommend following the steps detailed below to resolve the problem with the 'Requires Authentication' checkbox and the connection error between the Bravo environment and the orchestrator.
Analysis
The error message "Bravo environment was not able to connect to the orchestrator. The 'Requires Authentication' checkbox is not selected in the api service package" indicates that the authentication settings in the API service package are not correctly configured. This issue is consistent with several documented cases where the 'Requires Authentication' checkbox was not enabled, leading to connection failures between environments.
Proposed Solution
To resolve this issue, please follow these steps:
- Verify and Enable 'Requires Authentication' Checkbox:
- Navigate to the API service package in the Bravo environment.
- Ensure that the 'Requires Authentication' checkbox is selected.
- Save the changes.
- Update Client Secret and Authentication Profiles:
- Regenerate the client secret from the Orchestrator.
- Update the DMReleaseAdmin_OAuth2 authentication profile with the new client secret.
- Ensure that the Access token endpoint and Revoke token endpoint are correctly configured in the authentication profile.
- Perform a Rollover Restart:
- Perform a rollover restart of the Webuser PODs to ensure that all changes are applied correctly.
- Check Dynamic System Settings:
- Ensure that the dynamic system setting deploymentmanager/security/authentication/oauth/enabled is enabled in the owning ruleset PegaDevopsShared.
Root Cause
The root cause of this issue is the incorrect configuration of the 'Requires Authentication' checkbox in the API service package, which prevents the Bravo environment from authenticating and connecting to the orchestrator. Additionally, any discrepancies in the client secret and authentication profile settings can contribute to this problem.
https://support.pega.com/discussion/troubleshooting-connection-issues-b…
HCA Healthcare
US
Here’s a clean fix path. First, import the orchestrator’s SSL cert into every candidate’s truststore and confirm the token URL is right: /prweb/PRRestService/oauth2/v1/token. Next, use OAuth2 client-credentials only—disable “Use refresh token if available” (refresh tokens don’t apply to client-credentials). In DMReleaseAdmin_OAuth2 on each candidate, set the exact client id/secret from the orchestrator’s OAuth2 client registration, and verify the scope matches (or leave blank if not required). On the orchestrator, enable the api service package with Requires Authentication = checked and Authentication Type = OAuth2 (Basic won’t work for DM end-to-end). Ensure DMAgentUser (or DMReleaseAdmin) is unlocked, enabled, has the right access group, and that OrchestratorURL DSS is set correctly on candidates. Check clocks (NTP) to avoid token “nbf/exp” skew issues. Make sure ports/firewall allow candidates to reach the orchestrator over HTTPS. If you still see the “Requires Authentication” complaint after checking the box, clear caches/restart on both ends and retest—there’s no supported alternative to leaving that box unchecked for Deployment Manager.