Skip to main content

Appendix K: CyberArk Setup in PK Protect

This section describes the details to setup CyberArk in PK Protect.


  1. To enable SSL settings with certificate authentication in CyberArk:

    1. Obtain the CA signed certificate from CyberArk admin or authority for entry in keystore.

    2. Obtain the .pfx with password file from CyberArk admin or authority to create your keystore and truststore. You can also use extracted .jks file with the key password and keystore password.

    3. Obtain the RestAPI URL and Application ID that is holding your safe name and Object name. (Application must be associated with safe name)

    4. If you are using whitelist approach, ask the CyberArk admin to whitelist your IP in the application.

  2. To configure CyberArk’s AAM (Application Access Manager) Credential Provider with PK Protect:

    1. Define the Application ID (APP ID) and Authentication Details in CyberArk.

    2. The Application must have access to existing or new accounts to be provisioned in CyberArk vault. Once the accounts are managed by CyberArk, provide the access for these accounts to the Application and CyberArk Application Password Providers.

Perform the following steps in PK Protect:

  1. Go to  Settings > CyberArk Preferences under Admin and click Edit. After enabling the setting, enter the Safe Access URL and Application Id. Check the Certificate Authentication checkbox, if you want to enable CyberArk Certificate Authentication. Specify the Key Password, KeyStore Password, and path to the .jks file. It will automatically configure PK Protect for CyberArk.

  2. Go to NoSQL > Connection Manager > Add New Connection and create a CyberArk enabled NoSQL connection for the following databases: MongoDB, Cassandra, and CouchBase.

    Check the CyberArk Authentication checkbox and enter the Safe Name and Object Name. After successfully creating the connection, DSM Administrator connects with CyberArk and fetch the credentials for the user in that connection.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.