Close popover

Table of Contents

Configuring authentication profiles

Deployment Manager provides default operator IDs and authentication profiles. You must enable the default operator IDs and configure the authentication profiles that the orchestration server uses to communicate with the candidate systems.

Configure the default authentication profile by following these steps:

  1. On the orchestration server, enable the DMReleaseAdmin operator ID and specify its password.

    1. Log in to the orchestration server with administrator@pega.com/install.

    2. In the header of Dev Studio, click Records Organization Operator ID , and then click DMReleaseAdmin.

    3. On the Edit Operator ID rule form, click the Security tab.

    4. Clear the Disable Operator check box.

    5. Click Save.

    6. Click Update password.

    7. In the Change Operator ID Password dialog box, enter a password, reenter it to confirm it, and then click Submit.

    8. Log out of the orchestration server.

  2. On each candidate system, which includes the development, QA, staging, and production systems, enable the DMAppAdmin operator ID.

    If you want to create your own operator IDs, ensure that they point to the PegaDevOpsFoundation application.

    1. Log in to each candidate system with administrator@pega.com/install.

    2. In the header of Dev Studio, click Records Organization Operator ID , and then click DMAppAdmin.

    3. In the Explorer panel, click the operator ID initials, and then click Operator.

    4. On the Edit Operator ID rule form, click the Security tab.

    5. Clear the Disable Operator check box.

    6. Click Save.

    7. Click Update password.

    8. In the Change Operator ID Password dialog box, enter a password, reenter it to confirm it, and then click Submit.

    9. Log out of each candidate system.

  3. On each candidate system, update the DMReleaseAdmin authentication profile to use the new password. All candidate systems use this authentication profile to communicate with the orchestration server about the status of the tasks in the pipeline.

    1. Log in to each candidate system with the DMAppAdmin operator ID and the password that you specified.

    2. In the header of Dev Studio, click Records Security Authentication Profile .

    3. Click DMReleaseAdmin.

    4. On the Edit Authentication Profile rule form, click Set password.

    5. In the Password dialog box, enter the password, and then click Submit.

    6. Save the rule form.

  4. On the orchestration server, modify the DMAppAdmin authentication profile to use the new password. The orchestration server uses this authentication profile to communicate with candidate systems so that it can run tasks in the pipeline.

    1. Log in to the orchestration server with the DMAppAdmin user name and the password that you specified.

    2. In the header of Dev Studio, click Records Security Authentication Profile .

    3. Click DMAppAdmin.

    4. On the Edit Authentication Profile rule form, click Set password.

    5. In the Password dialog box, enter the password, and then click Submit.

    6. Save the rule form.

  5. If your target environment is SSL-enabled with private certificates, configure the Deployment Manager connectors so that they can receive and process tokens by doing setting the keystore:

    1. In the header of Dev Studio, create and configure a keystore. For more information, see Creating a keystore for application data encryption.

    2. Configure the Pega-DeploymentManager/TrustStore dynamic system setting to reference the keystore ID by clicking Records SysAdmin Dynamic System Settings .

    3. Click the Pega-DeploymentManager/TrustStore dynamic system setting.

    4. On the Settings tab, in the Value field, enter the ID of the keystore that you created in the previous step.

    5. Click Save.

    For more information about dynamic system settings, see Creating a dynamic system setting.

  6. Do one of the following actions:

  • Understanding default authentication profiles and operator IDs

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

Have a question? Get answers now.

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