Multiple PSM AWS Console Connector Failures (Session Termination & Selenium Driver Errors)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multiple PSM AWS Console Connector Failures (Session Termination & Selenium Driver Errors)

L1 Bithead

Description: We are experiencing two distinct connection issues across two newly deployed PSM servers while configuring the AWS Console with IAM user connection component (

PSM-AWS-IAM-User). Both issues prevent the automated browser session from launching successfully.

 

Issue 1: AppLocker / Secure Session Termination

Environment Details:

  • PSM Server: PSMServer_cyberark-1 (10.128.4.160)
  • Platform: SI-AWS-TEST-NEWPSM2

The connection successfully authenticates and routes to the PSM server, but immediately terminates before the browser launches, displaying the standard blue screen error: "This privileged session could not be established securely. Try to connect again through the Password Vault Web Access."

 

Issue2 — CyberArk PSM AWS Console Connector Fails to Load Browser Driver

Summary

The AWS Console with IAM user connection component (

PSM-AWS-IAM-User

 

) fails to launch a browser session on a newly deployed PSM server, throwing a "Selenium driver not found" error, despite the correct architecture-matched driver being present in the expected

DriverFolder

 

location. Root cause investigation points to a conflict between the connector's default browser configuration (Chrome) and the server's AppLocker hardening policy (which was pre-configured for Edge), compounded by AppLocker not whitelisting the

DriverFolder

execution path for the PSM session users.

Environment

ItemDetailCyberArk version14.9.1.2ComponentPrivileged Session Manager (PSM)PSM Server (affected)

PSMServer_cyberark-2

 

— 10.128.5.197 (Windows Server 2025 Datacenter, 10.0.26100)PlatformSI-AWS-TEST-NEWPSM (cloned from SI-AWS-TEST)Connection ComponentAWS Console with IAM user (

PSM-AWS-IAM-User

 

, config file

CC-AWS-IAM-User-MFA.xml

 

)Browser intended for useMicrosoft EdgeTargetAWS Console (526489132647.signin.aws.amazon.com)

Steps to Reproduce

1. Configure an AWS account object on Platform

SI-AWS-TEST-NEWPSM

 

, linked to PSM server

PSMServer_cyberark-2

.

2. Ensure the AWS Console with IAM user connector is associated with the platform.

3. From PVWA, select the account and click Connect → AWS Console with IAM user.

4. Session launches, then immediately closes with the following error:

 

Error Occurred

Session has been closed

Login failed

 

Failed to initialize web browser. Driver was not found.

Validate that the Selenium driver of the selected browser is located under 'DriverFolder'.

Expected Behavior

The AWS Console login page should open inside the recorded PSM session using Microsoft Edge, and the session should complete normally with a full-length recording available in PVWA.

Actual Behavior

Session terminates within seconds of launch with the above driver error, regardless of driver placement.

Investigation / Root Cause Analysis

1. Confirmed driver architecture: Initial

msedgedriver.exe

 

downloaded was ARM64, incompatible with the server's Intel Xeon x64 architecture (confirmed via

dxdiag

). Replaced with the correct x64 build matching the installed Edge version.

2. Confirmed driver presence in the documented location:

 

C:\Program Files (x86)\CyberArk\PSM\Components\DriverFolder\msedgedriver.exe

Test-Path

confirmed the file exists — error persisted regardless.

3. Found connector was still configured for Chrome, not Edge, in:

 

C:\Program Files (x86)\CyberArk\PSM\Components\Connectors\PSM-AWS-IAM-User\CC-AWS-IAM-User-MFA.xml

Original values:

 

xml

ClientApp="Chrome"

BrowserPath="C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

This server's AppLocker hardening rules (

PSMConfigureAppLocker.xml

 

) were pre-provisioned for Edge, not Chrome, indicating the connector's XML was never updated to match the intended browser during setup. Updated both

ClientApp

and

BrowserPath

to reference Edge — did not resolve the error on its own.

4. Found AppLocker was not whitelisting the DriverFolder path. The AppLocker hardening XML (

PSMHardening\PSMConfigureAppLocker.xml

) only had an

Allow

entry for:

 

C:\Program Files (x86)\CyberArk\PSM\Components\msedgedriver.exe

(Components root), not:

 

C:\Program Files (x86)\CyberArk\PSM\Components\DriverFolder\msedgedriver.exe

Confirmed via:

 

powershell

Get-AppLockerPolicy -Effective -Xml | Select-String "DriverFolder"

which returned no results — proving the effective (applied) policy did not whitelist the DriverFolder path at all, meaning any execution attempt from that path would be silently denied by AppLocker's default-deny Executable Rules for the

PSMConnect

/

PSMAdminConnect

session users.

5. Attempted to re-apply the corrected CyberArk hardening XML directly:

 

powershell

Set-AppLockerPolicy -XmlPolicy "C:\Program Files (x86)\CyberArk\PSM\Hardening\PSMConfigureAppLocker.xml" -Merge

This failed with:

 

The XML policy is invalid for the following reason: The 'PSMAppLockerConfiguration' element is not declared.

 

1 REPLY 1

L4 Transporter

Hi @sanjay sah​ Possible causes:

  1. AppLocker restrictions: AppLocker may be blocking execution from theComponents\DriverFolder\directory.
  2. Configuration mismatch: The connector XML may have been originally configured for Chrome, while the server hardening configuration is set up for Microsoft Edge. There could also be a version mismatch between Edge and EdgeDriver.
  3. Missing driver file: The required browser driver file may be missing from the expected location.

 

  • 42 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!