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.
@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 .
@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