Does the latest version of Deployment Manager 5 ( as of now version 5.6.2) support OAuth authentication type for communication between orchestrator to candidates as well as candidates to orchestrator ?
as per Deployment Manager 5.5.2 Pega API OAuth | Support Center it was planned to be supported in a future release.
Thanks,
@GeorgeH4322
This is not yet implemented communication from Orchestrator to Candidate still happens using basic authentication. May be we can discuss internally and can reply back here if we have a concrete release that we are going to support.
@GeorgeH4322 Though OOTB DM don’t support Basic Oauth communication between orchestrator to candidate. But client can use their custom authentication as mentioned in this Open Access Manager (OpenAM) integration with Deployment Manager link. Refer to pulse comments mentioned in link.
Hi @Pallavi Gurram, Could you share some insights on the APIs called by the orchestartor when performing “Deploy Application” task ? We are using OAUTH 2.0 in SystemManagement API in our candidate system. Upon troubleshooting understood that deploy application task on the orchestrator calls create restore point service method in SystemManagement service package (in the candidate system). This call fails as orchestartor uses basic auth and SystemManagement in our candidate system uses OAUTH. As suggested, we created a client registration for orchestrator in the candidate system and updated the generated client secret in an Authentication profile in orchestrator as well as referred the same auth profile in our deployment pipeline. Now the restore point api call is successful but deployment task fails with 401 error for another api call. Could you help resolve this issue?
@karthigeyanr this is a closed post and your question does not relate to the original topic.
Please use Ask a Question to post it as a new question. Feel free to tag the SME you wish to address your question to.
Please troubleshoot using the available resources
A deployment task in Deployment Manager can fail with a 401 error due to issues with the authentication profile configured in the Pipeline Settings under the External orchestration server tab. This error indicates an authorization problem which may arise if the OAuth 2.0 token is not valid or if the authentication profile is not correctly set up. It is essential to validate the authentication profile and ensure that the correct credentials are being used for the API calls.
Debugging Jenkins integration with Deployment Manger Issues
If product is not behaving as documented and you can replicate a product issue, log a support ticket via the My Support Portal which will allow our support engineers to investigate your scenario in detail.