Skip to main content

Specifying the default authentication method for new Pega Robot Manager users

Suggest edit Updated on October 7, 2021

Comply with your security requirements by selecting the authentication method that Pega Robot Manager assigns to a user role by default.

Before you begin: Depending on the implementation type, such as attended or unattended, update Pega Robotic Automation configuration as required. For more information, see Securing access to Pega Robot Manager.

When you add a user in Robot Manager, the authentication method for the user is determined by their access roles and the following dynamic system settings:

DefaultAuthenticationTypeForRuntimeOnlyUser
Determines the authentication method for users whose access group includes only the RuntimeUser access role. This setting does not apply to access groups that include more access roles in addition to RuntimeUser.
DefaultAuthenticationType
Determines the authentication method for access groups that do not meet the conditions for the DefaultAuthenticationTypeForRuntimeOnlyUser setting, for example, access groups that include Admin, UserAdmin, RobotAdmin, ReportAdmin, and Developer access roles.

For more information, see Default access roles.

  1. Specify the default authentication method for the RuntimeUser access role:
    1. In Dev Studio, click Records SysAdminDynamic System Settings.
    2. From the list of dynamic system settings, select DefaultAuthenticationTypeForRuntimeOnlyUser.
      Tip: Alternatively, use the Dev Studio search bar to quickly navigate to the setting that you want to update, as shown in the following example:
      Browsing dynamic system settings by using the Dev Studio search bar
      Use the Dev Studio search bar to quickly find a setting
                                            or a rule
    3. On the Settings tab, enter one of the following values:
      BasicSSO
    4. Confirm your configuration by clicking Save.
  2. Specify the default authentication method for user roles other than RuntimeUser:
    1. In Dev Studio, click Records SysAdminDynamic System Settings.
    2. From the list of dynamic system settings, select DefaultAuthenticationType.
    3. On the Settings tab, enter any of the following values:
      BasicSSO
    4. Confirm your configuration by clicking Save.
  3. If you configured any user role to authenticate by using the basic method, provide the temporary password for the first login:
    1. In Dev Studio, select RecordsTechnicalActivity.
    2. From the list of activities, select pyGetGeneratedPassword.
      You can quickly browse the activity list by filtering the Activity Name column.
    3. On the pyGetGeneratedPassword form, click Save as to specialize the rule in your application layer.
    4. On the pyGetGeneratedPassword form, click the Parameters tab.
    5. For the generatedPassword parameter, populate the Default value field with the temporary password for basic authentication users, as shown in the following example:
      Generating a temporary password for the first login
      You can generate a temporary password for basic
                                        authentication users
    6. Confirm your settings by clicking Save.
    Result: When a basic authentication user logs in to Pega Platform for the first time, the application prompts that user to enter the temporary password and then to provide the new password. In case of login issues, users can click the Forgot password? button to get a new temporary password.
What to do next: Create user accounts in Robot Manager either manually, or by importing a .csv file with a list of users. For more information, see Managing users.
  • Previous topic Updating the robotics configuration files for single sign-on authentication through Kerberos
  • Next topic Managing your organization in Pega Robot Manager
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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