Last activity: 5 Mar 2023 17:43 EST
Pega Deployment Manager Installation Issues
I am trying to install PDM 5.5, I am facing below issues with Orchestrator(Pega 8.6.2),
> Generated client secret from portal & tried to update auth profiles but getting issue with Access/Revoke token endpoints (Error : Please enter a valid URL including the protocol (http://, https:// etc.)) -PFA for the same (Note : we are using Tomcat 9)
> There is an error fetching details from Deployment Manager services http://xyz123.org.corp/prweb and Deployment Manager Studio will not function as expected. Please verify the configuration of the Orchestrator URL and authentication profiles configured. Error: Caught unhandled exception: com.pega.pegarules.pub.PRRuntimeException: PRRuntimeException
Tried the approach provided in this article Unable to configure pipeline in Deployment Manager 5.4 | Collaboration Center (pega.com) but no luck.
Can someone please advise?
***Edited by Moderator Marije to add Capability tags***
@VenkatTiyyagura Could you please review the suggestions at - oAuth FAQ ?
Review the OrchestratorURL DSS from General settings and do not forget to Save the change. When you try Generate client secret on General Settings, that should update the access\revoke token endpoints too. Ensure you are on HTTPS.
Thanks for your update.
I have checked the faqs earlier & tried them but it didnt work. Also we are on https, I generated client secret & updated the access & token endpoint urls manually to be sure. However, I have observed something strange, I have tried with dummy URL: xyz.org.net instead of xyz.org.corp - with the dummy URL the validation error is not coming.
@VenkatTiyyagura Do you get the same validation error when you try the generate client secret option from General settings? Could you please share the screenshot of the error on Deployment Manager?
@nayam , sure, I have generated client secret now again & clicked on update authentication profiles, I have attached the screenshot of the error. Thank you.
@VenkatTiyyagura Could you also share the downloaded client credentials?
@nayam , please find the attachment with the details.
Note : For privacy purpose I have updated the org & server name details.
@VenkatTiyyagura Looks like there is some issues in configuration. Could you please raise support request along with relavent error logs and tracer?
After raising a support request, please share its details (like ID number) for tracking it on this post.
Hi @GURRP1, Thanks for your response.
I dont think it is a configuration error because when I use net/us/nl/com or any other common extension instead of corp the validation is successful. I have verified the same in challenge environment from Pega academy as well, the result is same. Could you please verify & let us know if you still want us to raise an SR, then I will do it accordingly.
@VenkatTiyyagura Can you share the error/exception stack trace?
Hi @GURRP1, please find the error from logs with trace.
@VenkatTiyyagura Did you find any resolution for this issue. We are facing the same issue in our application
Updated: 17 Oct 2022 9:26 EDT
@SiriRamacharlu A hotfix was provided by Pega for this issue, after making that change we were able to save the rule properly & use PDM.
@VenkatTiyyagura What is the hotfix? Can you please provide me more details on this?