Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring authentication profiles on the orchestration server and candidate systems

Updated on April 5, 2022

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 doing these steps:

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

    1. Log in to the orchestration server with [email protected]/install.

    2. In Designer Studio, click RecordsOrganizationOperator ID, and then click DMReleaseAdmin.

    3. In the Designer Studio header, 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. Clear the Force password change on next login check box if you do not want to change the password for the DMReleaseAdmin operator ID the next time that you log in.

    10. Log out of the orchestration server.

  2. 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 user name and the password that you specified.

    2. Click RecordsSecurityAuthentication 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.

  3. 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 [email protected]/install.

    2. In the navigation pane of Designer Studio, click RecordsOrganizationOperator ID, and then click DMAppAdmin.

    3. In the header of Designer Studio, 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. Clear the Force password change on next login check box if you do not want to change the password for the DMReleaseAdmin operator ID the next time that you log in.

    10. Log out of each candidate system.

  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. Click RecordsSecurityAuthentication 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. Do one of the following actions:

    1. If you are upgrading to Deployment Manager 3.4.x, resume the upgrade procedure from step 2. For more information, see Upgrading to Deployment Manager 3.4.x.

    2. If you are not upgrading, continue the installation procedure. For more information, see Configuring the orchestration server.

  • Previous topic Configuring systems in the pipeline
  • Next topic Understanding default operator IDs and authentication profiles

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us