Pega RDA setup with package server and robot manager


I'm working on setting up an enterprise level pega RDA platform that uses both package server and robot manager to deploy the bots and any required components

Can someone help me understanding below items

  • User access management
  • Configuring Robot manager and package server in the dev studio and runtime resource

We are going to use only RDA, Any help would be appreciated


Keep up to date on this post and subscribe to comments

November 22, 2019 - 12:51pm

For enterprise RDA, you'll be using an identity provider. You can either use Kerberos, ADFS, or our own Security Token Service (STS). If your organization is already using Kerberos or ADFS, then you can configure that identity provider in your common config as a means of authenticating users to your Robot Manager instance.

If you do not already use either of those, then you can install and use the STS. I would suggest getting assistance here from either Pega or one of our partners as the initial setup is best done with someone with experience.

Once you have it setup, you can apply the same setting to Runtime and Studio in your CommonConfig. For Studio though, we typically use basic authentication where you have a user name and password to your Pega instance as several of the services accessed during development only work with basic authentication. These are mostly used for RPA though, so you probably would not encounter this strictly using RDA.