OAuth uses token-based authorization to grant operators access to their Robot Manager without sharing their credentials. A token is a unique identifier that the authorization server issues. The OAuth client uses that token to associate the request with the operator. The following diagram shows the architecture of how tokens are passed and verified when using OAuth:

The configuration process for OAuth 2.0 with SAML bearer includes obtaining the token-signing certificate, setting up the security authorization information in Pega Platform, and updating the configuration files as required.

1. Obtaining the token signing certificate for authenticating Pega Robot Manager users

   Obtain the token-signing certificate that contains cryptographic private and public keys that digitally sign a security token when authenticating Robot Manager users through OAuth 2.0 with SAML bearer.

2. Configuring Pega Robot Manager to support OAuth 2.0 with SAML bearer

   Allow Pega Robot Manager users to authenticate through OAuth 2.0 with SAML bearer by importing the token-signing certificate from the Security Token Service (STS) and configuring the client registration details in Robot Manager.

3. Adding a relying party

   Configure the Security Token Service as the entity that controls access to Pega Robot Manager.

4. Updating the robotics configuration files for SSO authentication through OAuth with SAML bearer

   Update the common configuration settings to authenticate attended robot operators and package publish requests in Pega Robot Manager through OAuth with SAML bearer.