Deployment Manager 5.5.2 Pega API OAuth
Hi All,
As per https://collaborate.pega.com/question/deployment-manager-merge-fails-when-pega-api-oauth-protected has this change been made available yet?
We are using Pega API service package with external systems for case creation and would like it to use OAuth.
Or is there a way around having it function without "Requires authentication" enabled on the api service package.
We are currently using PDM 4.8.2 and don't have an issue, but we'd like to upgrade to 5.5.2 but have encountered this problem that has a knock on affect to other systems.
Thanks
Craig
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
GB
Virgin Media
GB
@MarijeSchillern I'd already read these. But the FAQ was last updated in Dec 21 so I was hoping that OAuth had been implemented in latest release.
Updated: 20 May 2022 9:23 EDT
Pegasystems Inc.
IN
@CraigA52 This is not yet implemented communication from Orchestrator to Candidate still happens using basic authentication only but there are few customers who have used OAuth for CICD and API service packages but if encounter any issues that might not be prioritized because we have not tested and supporting that. In this case you have to create Authentication profile of type OAuth2 and refer in the pipeline , right now the default Authentication profile we use DMAppAdmin is of type Basic.
@CraigA52 please see the documentation Securely authenticating in Deployment Manager
There appears to have been no change. I will check with the SME to confirm.
Deployment Manager 5.1 now supports an OAuth 2.0 token-based authentication process for a more secure operator experience within the orchestrator and candidate environments
Also see Deployment Manager 5.2 - OAuth 2.0 - Dynamic Authentication Profile and Frequently asked questions (FAQs)
Can I use OAuth authentication type for communication between orchestrator and candidate?
Deployment manager currently uses OAuth for communication between candidate to orchestrator but communication from orchestrator to candidate is performed using basic authentication.
We are planning to support this in future releases.