- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-10-2024 04:03 AM
Guide for WEB access via PSM
Following the documentation I created this step-by-step guide, at the end of the post, I summarized the settings. For details with prints, download the file here.
------------------------------Step by step of the configuration I did.----------------------------------------
1.) Install the 32bit version of Chrome on the server.
2.) I downloaded and copied the chrome-driver from the same browser version and pasted C:\Program Files (x86)\CyberArk\PSM\Components.
3.) Set "$SUPPORT_WEB_APPLICATIONS" to true in the hardening script. (PSMHardening.ps1)
4.) I downloaded WebAppDispatcher (Secure Web Application Connectors Framework), unzipped and pasted all the folders into C:\Program Files (x86)\CyberArk\PSM, replacing
5.) I uncommented the chrome line in PSMConfigureApplocker.xml and ran hardening again.
6.0) I duplicated the "Amazon Web Services - AWS" platform, added the PSM and imported the plugin to access the AWS account. I used this one: https://cyberark.my.site.com/mplace/s/#a3550000000EiA9AAK-a3950000000jjSMAAY
6.1) I duplicated the "Amazon Web Services - AWS Access Keys" platform
7.) In the connection components > PSM-AWS-IAM-User I adjusted the following:
- Set the field to 60000: ConnectionComponentInitTimeout
- Set the field to 45: PageLoadTimeout
- Set the “RunValidations” field to “No”
- Adjust BrowserPath: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
8.) I onboarded the AWS account and key. I linked the key to the account.
This way, access worked, after setting App-Locker to audit-only. I need to see this adjusted.
------------------------END-------------------------------------------------------------------
02-10-2024 04:27 AM
Video demonstrating the configuration: https://youtu.be/YM5F60ReoDI
02-10-2024 04:50 AM
Issue 1: You are using ChromeDriver version 114 and Chrome version 121. They should match.
Issue 2: You are using Chrome 64-bit and probably are using ChromeDriver 32-bit. Use 32-bit for both - afaik PSM doesn't support 64-bit Chrome yet.
02-10-2024 11:24 AM
@Bernhard Brückler Thanks for the answer.
In the initial post, I adjusted the settings.
I redid the configuration and the access worked, but with App-Locker in audit-only.
What would be the configuration for access to work with app-locker enabled?
02-10-2024 11:54 AM
Is it necessary to add this line to release the DLLs from Chrome?
02-11-2024 03:58 AM
Now access is working, app-locker audit-only, but after 15s access is terminated.
The message appears and the session is closed:
"Session has been closed. Login failed. Validation failed. Refer the log for more information"
Have you seen this error? Any idea what might cause it?
LOG:
[11/02/2024 | 08:14:06] | :: | PSMDU014E Error performing dispatcher's request [GetSessionPropertyBufferLength]. Reason: PSMDU032E Session property [DriverFolder] is not present
[11/02/2024 | 08:14:06] | :: | PSMDU014E Error performing dispatcher's request [GetSessionPropertyBufferLength]. Reason: PSMDU032E Session property [WaitBeforeElementsLoad] is not present
[11/02/2024 | 08:14:06] | :: | PSMDU014E Error performing dispatcher's request [GetSessionPropertyBufferLength]. Reason: PSMDU032E Session property [PreConnectDllName] is not present
[11/02/2024 | 08:14:06] | :: | PSMDU014E Error performing dispatcher's request [GetSessionPropertyBufferLength]. Reason: PSMDU032E Session property [PreConnectParameters] is not present
[11/02/2024 | 08:14:29] | :: | PSMDU018E Dispatcher error: [HTMLPageController :: FindElement -> Timeout error. Element 'search-box-input' was not found in new page. ]
[11/02/2024 | 08:14:39] | :: | PSMDU018E Dispatcher error: [HTMLPageController :: FindElement -> Timeout error. Element 'mfacode' was not found in new page. ]
[11/02/2024 | 08:14:39] | :: | PSMDU018E Dispatcher error: [WebFormDispatcher :: HandleException -> CyberArk.WebAutomationCommon.ValidationExecuteException: Validation failed. Refer to the log for more information
at CyberArk.WebAutomationCommon.CommandsExecuter.RunValidationCommand(List`1 commands, Stack`1& commandsStack, CommandObject command)
at CyberArk.WebAutomationCommon.CommandsExecuter.RunCommands(List`1 commands, Boolean isRunValidation)
at CyberArk.WebAutomationCommon.WebPageExecuter.RunCommands(List`1 commands, Boolean isRunValidation)
at CyberArk.PSM.WebAppDispatcher.WebFormDispatcher.ExecuteLogin(IExecuter actionExecuter)]
[11/02/2024 | 08:14:39] | :: | PSMDU018E Dispatcher error: [ConnectionComponentController :: PopUpErrorMessageBox -> Title="Error Occurred" Message="Validation failed. Refer to the log for more information." Timeout=30 Subtitle="Login failed"]
02-12-2024 01:36 PM
Hi Tiago,
After accessing the URL, the validation process allows the cyberark to understand whether the URL was actually accessed. I have done this before by checking the value of an element on the page that opens after accessing the URL. You can check the document below.
https://docs.cyberark.com/pam-self-hosted/12.6/en/Content/PASIMP/psm_WebApplication.htm#Webformfields
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

