Question
TATA Consultancy Service
IN
Last activity: 30 Nov 2021 10:25 EST
Deployement manager studio is not functioning as expected
Hello All,
While we login to deployement manager, below error is been displayed in the studio.
Error:
There is an error fetching details from Deployment manager services https://xxxxxxxx:7050/prweb and Deployment manager Studio will not function as expected. Please verify the configuration of the Orchestration URL and authentication profiles configured.Error:Caught Exception while creating OAuth2 client
Deployement manager version: 5.1
orchestration and candidate systems version: 8.5.2
We have setup the orchestration and candidate systems as per the documentation, however it is failing with OAuth2 client authentication exception.
https://community.pega.com/knowledgebase/articles/devops/85/setting-orchestrator
All the configurations are done as per the documentation in PDN. Can someone please suggest how to resolve this issue?
Thank you.
Hello All,
While we login to deployement manager, below error is been displayed in the studio.
Error:
There is an error fetching details from Deployment manager services https://xxxxxxxx:7050/prweb and Deployment manager Studio will not function as expected. Please verify the configuration of the Orchestration URL and authentication profiles configured.Error:Caught Exception while creating OAuth2 client
Deployement manager version: 5.1
orchestration and candidate systems version: 8.5.2
We have setup the orchestration and candidate systems as per the documentation, however it is failing with OAuth2 client authentication exception.
https://community.pega.com/knowledgebase/articles/devops/85/setting-orchestrator
All the configurations are done as per the documentation in PDN. Can someone please suggest how to resolve this issue?
Thank you.
Pegasystems Inc.
IN
Hi @SunilY1721,
Can you please do below steps, even though it has been already done.
- Go to General > Settings
- Ensure that the Orchestrator URL is populated properly
- Press save (Even if Orchestrator URL was not updated)
- Press generate the client secret
- Press Download client secret and save it
- Press Update authentication profiles
- Log out, and log in
Nordea
SE
@ChinmayaHegde Hi, I think client certificate should be needed if we are setting up the oAuth communication channel. can we install and configure the latest DMGR without secure communication like we used to do in v4.8.x The idea is to explore the new features of DMGR
Pegasystems Inc.
IN
Hi @AnandP If you want to explore latest feature of DM 5.X then you should have https enabled orchestator and proper certificates for communication.
Nordea
SE
Hi,
is the issue resolved? I was having a similar issue while configuring the pipeline and I have performed all the steps as mentioned in the installation guide. For e.g. I have:-
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
Nordea
SE
The temporary workaround is to apply below DSS
DSS Name : https/allowAllHostnames Ruleset : Pega-IntegrationEngine value : true
Nordea
SE
You 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
Wipro
IN
@AnandP even i have this issue, i am fighting tooth and nail but still no luck.
Few basic questions.
To generate client secret https is mandatory ? since i am not using https setup, button to generate the client secrete is not visible, I so generated the client secret manually using - DeploymentManagerClient Oauth client button - Regenerate client secrete button. I have updated - DMStudioUser and DMAgentUser authentication profiles with this information but still my DM Portal is showing the same error.
I have created Keystore and trustore for both and DM and Candidate Server with Self Sign Certificate and updated all Auth Profile with this information.
What else is needed, why DM is failing , please give some points.
Nordea
SE
@RajeshKumarY6297 Hi, Your orchestrator should use secure communication using https and this is the basic requirement of using DMGR. However, you would also like to check if you have updated the DSS Truststore with value DMKeyStore.
As I mentioned earlier, try to set the below DSS and see if it works for you:--
DSS Name : https/allowAllHostnames Ruleset : Pega-IntegrationEngine value : true