LinkedIn
Copied!

Table of Contents

Understanding default authentication profiles and operator IDs

Version:

Only available versions of this content are shown in the dropdown

When you install Deployment Manager on all the systems in your ecosystem participating in the release process, there are applications, operator IDs, and authentication profiles installed by default. Authentication profiles enable communication between the orchestration server and candidate systems.

On the orchestration server, the following items are installed:

  • The Pega Deployment Manager application.
  • The DMReleaseAdmin operator ID, which release managers use to log in to the Pega Deployment Manager application. You must enable this operator ID and specify its password.
  • The DMAppAdmin authentication profile. The orchestration server uses this authentication profile to communicate with candidate systems so that it can run tasks in the pipeline. You must update this authentication profile to use the password that you specified for the DMAppAdmin operator ID, which is configured on all the candidate systems.
  • From version 5.x, Deployment Manager Service is the core system that the Portal and Agents are built on. The following items are installed:
    • The DMStudioUser authentication profile. The Deployment Manager Portal (GUI) uses this authentication profile to communicate with the Deployment Manager Services hosted on orchestrator system. Since the authentication profile type is oAuth2, the client secret gets updated by clicking the Generate client secret (Update authentication profile) button through the Deployment Manager Portal.
    • The DMAgentUser authentication profile. The Deployment Manager agent responsible for communicating task processes to candidate systems uses this authentication profile to fetch pending tasks from the Deployment Manager Services hosted on the orchestrator.

On all candidate systems, the following items are installed:

  • The PegaDevOpsFoundation application.
  • The DMAppAdmin operator ID, which points to the PegaDevOpsFoundation application. You must enable this operator ID and specify its password.
  • The DMReleaseAdmin authentication profile. All candidate systems use this authentication profile to communicate with the orchestration server about the status of the tasks in the pipeline. You must update this authentication profile to use the password that you specified for the DMReleaseAdmin operator ID, which is configured on the orchestration server.
  • From version 5.x, Deployment Manager Service is the core system that the Portal and Agents are built on. The following items are installed:
    • The DMReleaseAdmin_OAuth2 authentication profile. All candidate systems use this authentication profile to communicate with the orchestration server about the status of the tasks in the pipeline. Since the authentication profile type is oAuth2, the client secret must be updated with the client secret generated on the orchestrator (using the Generate client secret option from general settings on the Deployment Manager Portal).

The DMReleaseAdmin and DMAppAdmin operator IDs do not have default passwords.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.