Skip to main content


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

Understanding single sign-on authentication for Pega Robot Manager users

Updated on December 20, 2022

Use single sign-on (SSO) to access all your applications and to be able switch between applications without any additional actions.

In SSO, the application server extracts user credentials from a dedicated SSO server, and then checks the user against a directory of users.

SSO simplifies the login process by minimizing the likelihood of error because going through multiple login routines can lead to mistakes and always consumes more time.

Depending on your security policy requirements, in Pega Robot Manager, you can choose Kerberos or OAuth 2.0 with SAML bearer as your SSO standard for authenticating Robot Manager users.

Note: You can use single sign-on authentication for attended (Robotic Desktop Automation) robots only.

Learn more about authentication in Robot Manager with OAuth 2.0 with SAML bearer or Kerberos by reading one of the following articles:

  • Previous topic Updating the robotics configuration files for basic authentication
  • Next topic Authenticating Pega Robot Manager users through OAuth 2.0 with SAML bearer

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