Question
Department of Veterans Affairs
US
Last activity: 17 Jun 2021 9:55 EDT
Deployment Manager 5.2 - OAuth 2.0 - Dynamic Authentication Profile
Deployment Manager 5.2 uses OAuth 2.0 Token based authentication, to communicate between Orchestrator and Candidate systems. Is there a way to pass which OAuth 2.0 authentication profile to use on candidate system for connectors to communicate back to Orchestrator?
Reason: We develop and test pipelines in DEV Orchestrator and move to PROD Orchestrator where they cannot modify the pipelines. Since, there is only one authentication profile on candidate system, pipelines cannot be executed simultaneously from both DEV and PROD orchestrators.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
@VeeraRR Hi, Deployment Manager uses OAuth for communication from candidate to Orchestrator and communication from Orchestrator to candidate happens using Basic Authentication right now. Do you want to use different authentication profiles in different environments for communication from candidates to orchestrator ? the communication right now is happening using DMReleaseAdmin_OAuth2 and you will not see any issues even though you use same authentication profile .
Updated: 23 Apr 2021 9:40 EDT
Department of Veterans Affairs
US
@Goutham You're right. We have no issues with communications happening between Orchestrator to candidate which uses Basic Authentication
Issue is when Candidate communicates back to Orchestrator . We cannot use same DMReleaseAdmin_OAuth2 to communicate back to either DEV and PROD Orchestrator without changing the DMReleaseAdmin_OAuth2 settings.
Is there something where we can pass dynamic OAauth (DMReleaseAdmin_OAuth2) profile from DEV or PROD Orchestrator so that candidate knows which one to use to communicate back
Pegasystems Inc.
IN
@VeeraRR So what I understand is you have 2 orchestrator systems using the same candidates system and you want to communicate to both of them from candidate systems right ?
Pegasystems Inc.
IN
@VeeraRR we cannot do that we have DASS to use different Authentication Profile but that will be used in all cases, you cannot override based on the orchestrator system.
Department of Veterans Affairs
US
@Goutham Is there a way to provide enhancement to pass DMReleaseAdmin_OAuth2 profile from Orchestrator similar to how we pass DMAppAdmin for each stage ?