Issue retrieving password after integrating with CyberArk


We are currently testing UiPath integration with CyberArk. The CyberArk configurations have been completed. The agent has been installed on the Orchestrator machine and the password retrieval works fine with CLI. But after setting up CyberArk as a Credential Store and creating a new robot, the password retrieval fails when trying to launch a job. Here is the error test:

[4:25 PM] Ranjani Lobo (Contractor)
    RemoteException wrapping System.ArgumentNullException: Value cannot be null.
Parameter name: password
at UiPath.Service.PasswordCredential..ctor(UserIdentity user, SecureString password)
at UiPath.Service.Orchestrator.NotificationProcessor.d__14.MoveNext()


Hello @rlobo!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly

Hi @rlobo,

Did you every resolve your issue? If so would you mind updating the post with your solution?

When I configured CyberArk Integration and ran into a similar issue AAM CLI was successful but Orchestrator was failing to retrieve it was generally a typo in the Credential Store configuration or Credential’s reference on the Username or External Name.