Configuring authentication for Pega Robot Manager
Configure authentication requirements for user roles before creating users in Pega Robot Manager.
By default, all users authenticate by using basic authentication. RPA Runtime users authenticate with the registration operator account for registration purposes, and then automatically sign on through basic authentication by using a generated password. RDA Runtime users use basic authentication as a default.
Pega Robot Manager supports basic authentication and single sign-on (SSO) by using either OAuth 2.0 with SAML bearer assertion or Kerberos.
When you create user accounts in Pega Robot Manager, the authentication method that is assigned to each user is determined by their specified role and the dynamic system setting that is associated with the specified role.
- Configuring OAuth 2.0 with SAML bearer assertion for single sign-on
- Configuring Kerberos authentication for single sign-on
By default, robots log in to Pega Platform by using basic authentication. You can configure Pega Robot Manager to use Kerberos authentication for robots.
- Enabling Pega Platform to support Kerberos single sign-on
On a running Active Directory (AD) server, you can enable Pega Platform, running on an Apache Tomcat server, to use Kerberos authentication.
- Specifying the Kerberos authentication method that Pega Platform uses
Configure the EnableDefaultKerberosAuthenticationForRobotManger dynamic system setting to specify which Kerberos authentication method you want to use to authenticate traffic to Pega Robot Manager.