I'm currently working with our resident security guy to integrate Robotics 19.1/Robot Manager 8.3 with CyberArk, as that is the preferred method for managing our credentials (over DPAPI). We've run into a bit of a snag, however.
The way to do this seems to be to install the CyberArk Credential Provider on the master VM, so that all "satellite" VMs have the CP, and then use it to get credentials indirectly from the CyberArk server. However, due to some confusion over licensing, we have to speak to CyberArk reps to make sure we're setting it up correctly.
The URL below is where you would start. As I am told, once you configure Runtime and your RPA service to use use CyberArk, all credential retrieval is done through CyberArk AIM. In your solution for example if you needed credentials to login to a website, you could use the CredentialStore component and provide it the name of the credential in CyberArk AIM and that component would retrieve it from AIM. For the Registration Operator, Windows User, etc...those would be retrieved by the RPA service via AIM.
That's the first one I found, then followed the links at the bottom. It seems like the Credential Provider needs to be installed locally for it to work, but I can try it without installing that.
The link at the bottom of that page that you linked goes to the help site for Common Configuration Settings. Under "Servers" on that page, under CredentialManager it says "Contact Robotic Automation Support before enabling the CredentialManager server type". That's the only place I can see to specify our actual server address.
RonaldB2 - Were you able to get past this technical snag? We are also in need of some suggestions to implement Cyber Ark with 19.1 version and we are stuck with the same issue as you reported. Any help that you can offer from your progress will help.