Question
Nordea
SE
Last activity: 23 Nov 2021 11:05 EST
Unable to configure pipeline in Deployment Manager 5.4
Hi,
While configuring the deployment manager pipeline, we are getting the below error on the page:--
There is an error fetching details from Deployment Manager services https://XXXXXX/prweb and Deployment Manager Studio will not function as expected. Please verify the configuration of the Orchestrator URL and authentication profiles configured. Error: Caught Exception while creating OAuth2 client
Deployment manager version: 5.4
Orchestrator version: v8.6.2
Candidate version: v8.6.1
I have set up the Orchestrator as mentioned in the installation guide here - https://docs-previous.pega.com/devops/86/setting-orchestrator which include:--
1) Generated client secrets and updated authentication profile
2) DMStudiouser and DMAgentUser Auth profiles are configured with the correct access and revoke token endpoints
3) Uploaded proper Keystore in DMKeystore rule
4) Password and Alias for Keystore are correct in DeploymentManagerClientJWTProfile token profile security section
A similar issue was also reported in another community post - https://collaborate.pega.com/question/deployement-manager-studio-not-functioning-expected and I can't see any proper outcome.
Can someone please advise?
***Edited by Moderator: Pooja Gadige to add capability tag***
Accepted Solution
Nordea
SE
This is now fixed for secure communication. We need to follow the below steps which are not mentioned in the installation guide and Pega should update that:--
a) Update the Truststore of DMAgentUser and DMStudioUser Authentication profile in Orchestrator with the DMKeyStore rule
b) Update the Truststore of DMReleaseAdmin_OAuth2 Authentication profile in Candidate environments with the DMKeyStore rule
Please note DMKeyStore rule will contain the self-signed certificates of your environment and for more details, you can refer to - https://docs-previous.pega.com/security/86/creating-keystorejks-and-truststorejks-files
Accepted Solution
Nordea
SE
This is now fixed for secure communication. We need to follow the below steps which are not mentioned in the installation guide and Pega should update that:--
a) Update the Truststore of DMAgentUser and DMStudioUser Authentication profile in Orchestrator with the DMKeyStore rule
b) Update the Truststore of DMReleaseAdmin_OAuth2 Authentication profile in Candidate environments with the DMKeyStore rule
Please note DMKeyStore rule will contain the self-signed certificates of your environment and for more details, you can refer to - https://docs-previous.pega.com/security/86/creating-keystorejks-and-truststorejks-files