Skip to main content

Understanding basic authentication for Pega Robot Manager users

Suggest edit Updated on October 7, 2021

Basic authentication works by prompting the user for a user name and password, which Pega Platform validates against the credentials that are stored in the Pega database. In this method, the authentication information is retrieved from the server with just one call, which makes that method faster than other, more complex authentication mechanisms.

The management and login process for robot operators depends on your implementation type.

Attended robot operators

When using attended robot operators, the case worker (for example, a call center agent) must start Pega Robot Runtime manually on their desktop and provide the login credentials, so that the robot operator can download the automation package and start working. Every time the password of the robot operator changes (either because of password expiration, or because of a forced change during the first-time login of a new operator), the case worker must manually change the password in Pega Platform, as shown in the following example:

Basic authentication for attended robot operators
Case workers must change the default robot operator password in Pega
                            Platform every time that password expires or is no longer valid

Unattended robot operators

To securely connect robot operators to Robot Manager and maintain operational flexibility, the RPA service needs three operator types involved for one robot operator to run:

Registration sequence for unattended robot operators in basic authentication
Pega Robot Manager needs three operator types to securely authenticate
                            a robot when using basic authentication

The following table provides a description of each step in the registration sequence of unattended robot operators:

StepDescriptionAdditional information
1The RPA service uses the registration operator at the beginning of a robot session to start and authenticate the service connection with Pega Robot Manager.

The registration operator is the only operator type you must provision and whose password you can change.

For more information, see:

2

After the RPA service authenticates, it switches to the newly created RPA service operator.

The RPA service operator manages Windows sessions of robot operators by starting, stopping or scheduling Pega Robot Runtime.

You specify this operator's name in the CommonConfig.xml file by updating the RPAServiceOperator parameter.

For more information, see Updating the robotics configuration files for basic authentication.

3When started by the RPA service, Pega Robot Runtime establishes the initial connection to Robot Manager by using the registration operator. Then, Pega Robot Runtime switches to the Runtime operator.

You specify this operator's name in the in the CommonConfig.xml file by updating the robotName parameter.

Runtime operator is the robot that uses the GetNextWork function and is visible in the Robot Manager interface.

For more information, see Updating the robotics configuration files for basic authentication.

Configure Robot Manager users for basic authentication by completing the following process:

  • Previous topic Learning about the supported authentication mechanisms for Pega Robotic Automation components
  • Next topic Authenticating Pega Robot Manager users through the basic method
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support 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