Orchestrator to Development: Fail: Unexpected HTTP 403 Response code
I have been facing this issue since late Jan 2024. We haven't changed any setup of the pipeline/cicd package/ connection setting. However, one day it suddenly returned this kind of error when Orchestrator to Development:
An authorization issue occurred in the cicd package on the Development environment. Possible reasons include:
1. The authentication type may not be appropriate.
2. Make sure that the 'Require TLS/SSL for REST services in this package' checkbox is unchecked in the cicd package.
3. Target application is not built on 'PegaDevopsFoundation'.
We have tried to adjust uncheck the 'Require TLS/SSL for REST services in this package' checkbox but it still doesn't work. And we are sure that the application is built on 'PegaDevopsFoundation'.
This error is blocking the deployment in our dev environment.
Pegasystems Inc.
GB
@Valor please can you confirm you are using a compatible stack as per
The HTTP 403 error usually indicates a client error, often related to permissions or authentication. In the context of Deployment Manager, this error can occur due to several reasons:
- Incorrect configuration of the Orchestrator URL or authentication profiles.
- The operator's access group doesn't have the required permissions.
- The operator is not pointing to the correct default access group, which should be a superadmin AG from the Deployment Manager application.
- The password for the DMAppAdmin Authentication profile in the Orchestrator and the password for the DMAppAdmin operator in the candidate environment are not the same.
Did you carry out a platform upgrade to your orchestrator system to 8.8.4 to match with Candidate systems, so that DM 5.x can be used?
Can you share the orchestrator and staging url to check the communication? Ip whitelisting is required for environments to communicate .
@Valor please can you confirm you are using a compatible stack as per
The HTTP 403 error usually indicates a client error, often related to permissions or authentication. In the context of Deployment Manager, this error can occur due to several reasons:
- Incorrect configuration of the Orchestrator URL or authentication profiles.
- The operator's access group doesn't have the required permissions.
- The operator is not pointing to the correct default access group, which should be a superadmin AG from the Deployment Manager application.
- The password for the DMAppAdmin Authentication profile in the Orchestrator and the password for the DMAppAdmin operator in the candidate environment are not the same.
Did you carry out a platform upgrade to your orchestrator system to 8.8.4 to match with Candidate systems, so that DM 5.x can be used?
Can you share the orchestrator and staging url to check the communication? Ip whitelisting is required for environments to communicate .
Also review the Service Access Group for cicd service package is the same on the Pipeline details. Can you confirm which Access group needs to be used and make this the same for the pipeline and cicd package?
Please log a support issue and let us know the INC here if you need further help.