Configure a CyberArk Agent

  1. Execute the following command to move the RHELinuxx64-Rls-v9.9.zip package to /root in the AppViewX Server: mv RHELinux x64-Rls-v9.9.zip /root
  2. Untar the package by entering the following command: unzip RHELinux x64-Rls-v9.9.zip
  3. Rename the package by entering the following command: mv RHELinux x64 RHELinux_64
  4. Navigate to the RHELinux_64 directory and execute the following commands to change the Read/Write/Execute permissions for the CreateCredFile:
    cd RHELinux_64/
    chmod 755 CreateCredFile 
  5. Enter the following command to provide the username and its associated password for the CyberArk Vault Administrator:./CreateCredFile administrator.cf Password
    Note: Leave the remaining parameters set to the default value.
  6. Modify the following fields in the /root/RHELinux_64/aimparms.sample file by entering the command vi aimparms.sample:
    • AcceptCyberArkEULA=Yes
    • CreateVaultEnvironment=yes
    • LicensedProducts=AIM
    • CredFilePath=/root/RHELinux_64/administrator.cf
    • VaultFilePath=/root/RHELinux_64/Vault.ini
  7. Click Save.
  8. Copy the aimparms.sample file to /var/tmp/aimparms by entering the following command: cp aimparms.sample /var/tmp/aimparms
  9. Modify the following fields in the /root/RHELinux_64/Vault.ini file by entering the command vi Vault.ini
    • VAULT = <"Vault name">
    • ADDRESS=<CyberArk vault address>
    • PORT=<CyberArk vault listening port>
    Note: These details must be fetched from the CyberArk team.
    Note: Before installation, ensure that the RPM package (such as the IP address and Port number) must be reachable from Agent Server.
  10. Click Save.
  11. Install the RPM package CARKaim-9.80.0.85.x86_64.rpm by entering the following command: rpm -i CARKaim-9.80.0.85.x86_64.rpm
  12. After installing the RPM package, execute the following command to check the service status: service aimprv status.
    The response is displayed as Cyber-Ark Application Password Provider is running
After the service is up and running, it allows the agent server hostname as a member for all the safes on the CyberArk component, for which the credentials have to be retrieved from the vault.