Question
How do I configure the PSM-PrivateArkClient connection component to open a recorded PSM session to the PrivateArk Client?
Answer
Follow these steps below:
NOTE:
- One of the installation steps requires a restart of the PSM server (change control).
- 'PrivateArkConfigurationData.ini' must not contain any spaces or other special characters other than '.'
When installing the PrivateArk Client on the PSM server. Ignore (Click OK) the warning about the IE proxy configuration.
These are the steps to set the global configuration for the Private Ark client if it's already installed:
1. Login to the Private Ark Client as Administrator and go to Tools --> Administrative Tools --> Export Configuration Data.
2. Make sure "Export Global Configuration Data" is checked.
3. Rename the "PrivateArk Configuration Data.ini" file to PrivateArkConfigurationData.ini (Remove the spaces)
Note: This must be unique for each PSM as vaultID is a unique value
4. Select a place to save the configuration data on the PSM server.
5. Open a command prompt as administrator.
6. Go to the Private Ark Client installer directory (usually C:\Program Files (x86)\PrivateArk\Client).
7. Run PAConfig.exe /inifile <complete path and file name of the global config file you exported in step 3> - Please Note: You have to put the full path(s) in quotes.
Example:
"C:\Program Files (x86)\PrivateArk\Client\PAConfig.exe" /inifile "C:\Program Files (x86)\PrivateArk\Client\PrivateArkConfigurationData.ini"
Note:
This command writes a change to the HKLM\SOFTWARE\WOW6432Node\CyberArk\PrivateArk\ConfigInfo\Global:TargetName registry key as the full path to the file, without quotes
8. Reboot the PSM server.
After reboot:
9. Go to the directory of the global config file (INI) and edit it.
10. Make sure these two lines match the following:
[CyberArk\PrivateArk\Client\Servers\<IP address of vault server>]
ServerName=<IP address of vault server>
You must use the IP address in both lines, not the NAME. - otherwise you will get an error when launching the client:
"The Session could not be established and therefore will be closed. For further assistance, please contact your system administrator".
You will also see in the log:
PSMDU019I Dispatcher trace message: [PSM-PrivateArkClientDispatcher Dispatcher - Failed to find server [x.x.x.x] in list of configured servers]
Example:
[CyberArk\PrivateArk\Client\Servers\10.0.1.10]
ServerName=10.0.1.10
11. Make sure the PSMShadowUsers group has basic read/execute access to the folder where the global config file is. You may have to add the PSMShadowUsers group to the folder's access list.
Note: The following command can be run in an elevated command prompt to ensure this;
PowerShell -c '({$PAClientDir = $(Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\CyberArk\PrivateArk\Client").PrivateArkDirectory;$Ar = get-acl $PAClientDir;$Ar.SetAccessRule($(new-object System.Security.AccessControl.FileSystemAccessRule($("$env:COMPUTERNAME\PSMShadowUsers"),"ReadAndExecute","Allow")));Set-Acl $PAClientDir $Ar})'
12. You can choose which ever authentication method you want, but you can only use one as a default if you want the username and password fields automatically populated for logon. You can set the default authentication method on the PA Client on the PSM by going to the logon page and clicking the Advanced button. Then select one of the authentication methods listed and click OK.
13. Create an account in PVWA with credentials that can log on to the PrivateArk Client based on the authentication type chosen in the previous step. Use PLATFORM: 'Idira Vault', TYPE: 'Application', and create or pick a safe in which to store the credentials. If using LDAP, do not use the domain prefix (domain\account). This will not work because the '\' character is not accepted and will throw an error.
14. Test the connector.
Note: You can also check for any errors in the log file for the PAclient in the specific PSMshadowuser's profile in:
C:\Users\<psmshadowuser>\AppData\Roaming\CyberArk\PrivateArk\PALog.txt
Q: How do I configure the PSM-PrivateArkClient connection component to open a recorded PSM session to the PrivateArk Client?
A: Follow these steps below:
NOTE: One of the installation steps requires a restart of the PSM server (change control).
When installing the PrivateArk Client on the PSM server. Ignore (Click OK) the warning about the IE proxy configuration.
These are the steps to set the global configuration for the Private Ark client if it's already installed:
1. Login to the Private Ark Client as Administrator and go to Tools --> Administrative Tools --> Export Configuration Data.
2. Make sure "Export Global Configuration Data" is checked.
3. Rename the "PrivateArk Configuration Data.ini" file to PrivateArkConfigurationData.ini (Remove the spaces)
3. Select a place to save the configuration data on the PSM server.
4. Open a command prompt as administrator.
5. Go to the Private Ark Client installer directory (usually C:\Program Files (x86)\PrivateArk\Client).
6. Run PAConfig.exe /inifile <complete path and file name of the global config file you exported in step 3> - Please Note: You have to put the full path(s) in quotes.
Example:
"C:\Program Files (x86)\PrivateArk\Client\PAConfig.exe" /inifile "C:\Program Files (x86)\PrivateArk\Client\PrivateArkConfigurationData.ini"
Note:
This command writes a change to the HKLM\SOFTWARE\WOW6432Node\CyberArk\PrivateArk\ConfigInfo\Global:TargetName registry key as the full path to the file, without quotes
7. Reboot the PSM server.
After reboot:
8. Go to the directory of the global config file (INI) and edit it.
9. Make sure these two lines match the following:
[CyberArk\PrivateArk\Client\Servers\<IP address of vault server>]
ServerName=<IP address of vault server>
You must use the IP address in both lines, not the NAME. - otherwise you will get an error when launching the client:
"The Session could not be established and therefore will be closed. For further assistance, please contact your system administrator".
You will also see in the log:
PSMDU019I Dispatcher trace message: [PSM-PrivateArkClientDispatcher Dispatcher - Failed to find server [x.x.x.x] in list of configured servers]
Example:
[CyberArk\PrivateArk\Client\Servers\10.0.1.10]
ServerName=10.0.1.10
10. Make sure the PSMShadowUsers group has basic read/execute access to the folder where the global config file is. You may have to add the PSMShadowUsers group to the folder's access list.
Note: The following command can be run in an elevated command prompt to ensure this;
PowerShell -c '({$PAClientDir = $(Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\CyberArk\PrivateArk\Client").PrivateArkDirectory;$Ar = get-acl $PAClientDir;$Ar.SetAccessRule($(new-object System.Security.AccessControl.FileSystemAccessRule($("$env:COMPUTERNAME\PSMShadowUsers"),"ReadAndExecute","Allow")));Set-Acl $PAClientDir $Ar})'
11. You can choose which ever authentication method you want, but you can only use one as a default if you want the username and password fields automatically populated for logon. You can set the default authentication method on the PA Client on the PSM by going to the logon page and clicking the Advanced button. Then select one of the authentication methods listed and click OK.
12. Create an account in PVWA with credentials that can log on to the PrivateArk Client based on the authentication type chosen in the previous step. Use PLATFORM: 'Idira Vault', TYPE: 'Application', and create or pick a safe in which to store the credentials. If using LDAP, do not use the domain prefix (domain\account). This will not work because the '\' character is not accepted and will throw an error.
13. Test the connector.
Note: You can also check for any errors in the log file for the PAclient in the specific PSMshadowuser's profile in:
C:\Users\<psmshadowuser>\AppData\Roaming\CyberArk\PrivateArk\PALog.txt