Authenticating Pega Robot Manager users through OAuth 2.0 with SAML bearer
Comply with your security policy by configuring Pega Robot Manager operators to use OAuth 2.0 with SAML bearer to authenticate across multiple applications with a single set of credentials.
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.
- 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.
- 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.
- Adding a relying party
Configure the Security Token Service as the entity that controls access to Pega Robot Manager.
- 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.
Previous topic Understanding single sign-on authentication for Pega Robot Manager users Next topic Obtaining the token signing certificate for authenticating Pega Robot Manager users