<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Multiple PSM AWS Console Connector Failures (Session Termination &amp; Selenium Driver Errors) in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-psm-aws-console-connector-failures-session-termination/m-p/1409262#M5975</link>
    <description>&lt;P&gt;Hi @sanjay sah​&amp;nbsp;Possible causes:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;AppLocker restrictions: AppLocker may be blocking execution from theComponents\DriverFolder\directory.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;Missing driver file: The required browser driver file may be missing from the expected location.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 14 Aug 2026 06:04:50 GMT</pubDate>
    <dc:creator>PY</dc:creator>
    <dc:date>2026-08-14T06:04:50Z</dc:date>
    <item>
      <title>Multiple PSM AWS Console Connector Failures (Session Termination &amp; Selenium Driver Errors)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-psm-aws-console-connector-failures-session-termination/m-p/1409261#M5974</link>
      <description>&lt;P&gt;&lt;B&gt;Description:&lt;/B&gt; We are experiencing two distinct connection issues across two newly deployed PSM servers while configuring the AWS Console with IAM user connection component (&lt;/P&gt;&lt;P&gt;PSM-AWS-IAM-User). Both issues prevent the automated browser session from launching successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue 1: AppLocker / Secure Session Termination&lt;/P&gt;&lt;P&gt;&lt;B&gt;Environment Details:&lt;/B&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;B&gt;PSM Server:&lt;/B&gt; PSMServer_cyberark-1 (10.128.4.160)&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Platform:&lt;/B&gt; SI-AWS-TEST-NEWPSM2&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The connection successfully authenticates and routes to the PSM server, but immediately terminates before the browser launches, displaying the standard blue screen error: &lt;I&gt;"This privileged session could not be established securely. Try to connect again through the Password Vault Web Access."&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Issue2 — CyberArk PSM AWS Console Connector Fails to Load Browser Driver&lt;/P&gt;&lt;P&gt;Summary&lt;/P&gt;&lt;P&gt;The &lt;B&gt;AWS Console with IAM user&lt;/B&gt; connection component (&lt;/P&gt;&lt;P&gt;PSM-AWS-IAM-User&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;) 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&lt;/P&gt;&lt;P&gt;DriverFolder&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;DriverFolder&lt;/P&gt;&lt;P&gt;execution path for the PSM session users.&lt;/P&gt;&lt;P&gt;Environment&lt;/P&gt;&lt;P&gt;ItemDetailCyberArk version14.9.1.2ComponentPrivileged Session Manager (PSM)PSM Server (affected)&lt;/P&gt;&lt;P&gt;PSMServer_cyberark-2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;— 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 (&lt;/P&gt;&lt;P&gt;PSM-AWS-IAM-User&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;, config file&lt;/P&gt;&lt;P&gt;CC-AWS-IAM-User-MFA.xml&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;)Browser intended for useMicrosoft EdgeTargetAWS Console (&lt;A alt="http://526489132647.signin.aws.amazon.com" href="http://526489132647.signin.aws.amazon.com" target="_blank"&gt;526489132647.signin.aws.amazon.com&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;Steps to Reproduce&lt;/P&gt;&lt;P&gt;1. Configure an AWS account object on Platform&lt;/P&gt;&lt;P&gt;SI-AWS-TEST-NEWPSM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;, linked to PSM server&lt;/P&gt;&lt;P&gt;PSMServer_cyberark-2&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;2. Ensure the &lt;B&gt;AWS Console with IAM user&lt;/B&gt; connector is associated with the platform.&lt;/P&gt;&lt;P&gt;3. From PVWA, select the account and click &lt;B&gt;Connect → AWS Console with IAM user&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;4. Session launches, then immediately closes with the following error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Error Occurred&lt;/P&gt;&lt;P&gt;Session has been closed&lt;/P&gt;&lt;P&gt;Login failed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Failed to initialize web browser. Driver was not found.&lt;/P&gt;&lt;P&gt;Validate that the Selenium driver of the selected browser is located under 'DriverFolder'.&lt;/P&gt;&lt;P&gt;Expected Behavior&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Actual Behavior&lt;/P&gt;&lt;P&gt;Session terminates within seconds of launch with the above driver error, regardless of driver placement.&lt;/P&gt;&lt;P&gt;Investigation / Root Cause Analysis&lt;/P&gt;&lt;P&gt;1. &lt;B&gt;Confirmed driver architecture:&lt;/B&gt; Initial&lt;/P&gt;&lt;P&gt;msedgedriver.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;downloaded was ARM64, incompatible with the server's Intel Xeon x64 architecture (confirmed via&lt;/P&gt;&lt;P&gt;dxdiag&lt;/P&gt;&lt;P&gt;). Replaced with the correct x64 build matching the installed Edge version.&lt;/P&gt;&lt;P&gt;2. &lt;B&gt;Confirmed driver presence in the documented location:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;   C:\Program Files (x86)\CyberArk\PSM\Components\DriverFolder\msedgedriver.exe&lt;/P&gt;&lt;P&gt;Test-Path&lt;/P&gt;&lt;P&gt;confirmed the file exists — error persisted regardless.&lt;/P&gt;&lt;P&gt;3. &lt;B&gt;Found connector was still configured for Chrome, not Edge&lt;/B&gt;, in:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;   C:\Program Files (x86)\CyberArk\PSM\Components\Connectors\PSM-AWS-IAM-User\CC-AWS-IAM-User-MFA.xml&lt;/P&gt;&lt;P&gt;Original values:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;xml&lt;/P&gt;&lt;P&gt;   ClientApp="Chrome"&lt;/P&gt;&lt;P&gt;   BrowserPath="C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"&lt;/P&gt;&lt;P&gt;This server's AppLocker hardening rules (&lt;/P&gt;&lt;P&gt;PSMConfigureAppLocker.xml&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;) were pre-provisioned for &lt;B&gt;Edge&lt;/B&gt;, not Chrome, indicating the connector's XML was never updated to match the intended browser during setup. Updated both&lt;/P&gt;&lt;P&gt;ClientApp&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;BrowserPath&lt;/P&gt;&lt;P&gt;to reference Edge — did not resolve the error on its own.&lt;/P&gt;&lt;P&gt;4. &lt;B&gt;Found AppLocker was not whitelisting the DriverFolder path.&lt;/B&gt; The AppLocker hardening XML (&lt;/P&gt;&lt;P&gt;PSMHardening\PSMConfigureAppLocker.xml&lt;/P&gt;&lt;P&gt;) only had an&lt;/P&gt;&lt;P&gt;Allow&lt;/P&gt;&lt;P&gt;entry for:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;   C:\Program Files (x86)\CyberArk\PSM\Components\msedgedriver.exe&lt;/P&gt;&lt;P&gt;(Components &lt;B&gt;root&lt;/B&gt;), not:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;   C:\Program Files (x86)\CyberArk\PSM\Components\DriverFolder\msedgedriver.exe&lt;/P&gt;&lt;P&gt;Confirmed via:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;powershell&lt;/P&gt;&lt;P&gt;   Get-AppLockerPolicy -Effective -Xml | Select-String "DriverFolder"&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;PSMConnect&lt;/P&gt;&lt;P&gt;/&lt;/P&gt;&lt;P&gt;PSMAdminConnect&lt;/P&gt;&lt;P&gt;session users.&lt;/P&gt;&lt;P&gt;5. &lt;B&gt;Attempted to re-apply the corrected CyberArk hardening XML directly:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;powershell&lt;/P&gt;&lt;P&gt;   Set-AppLockerPolicy -XmlPolicy "C:\Program Files (x86)\CyberArk\PSM\Hardening\PSMConfigureAppLocker.xml" -Merge&lt;/P&gt;&lt;P&gt;This failed with:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;   The XML policy is invalid for the following reason: The 'PSMAppLockerConfiguration' element is not declared.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2026 12:59:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-psm-aws-console-connector-failures-session-termination/m-p/1409261#M5974</guid>
      <dc:creator>VDhake</dc:creator>
      <dc:date>2026-07-02T12:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple PSM AWS Console Connector Failures (Session Termination &amp; Selenium Driver Errors)</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-psm-aws-console-connector-failures-session-termination/m-p/1409262#M5975</link>
      <description>&lt;P&gt;Hi @sanjay sah​&amp;nbsp;Possible causes:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;AppLocker restrictions: AppLocker may be blocking execution from theComponents\DriverFolder\directory.&lt;/LI&gt;&lt;LI&gt;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.&lt;/LI&gt;&lt;LI&gt;Missing driver file: The required browser driver file may be missing from the expected location.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Aug 2026 06:04:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-psm-aws-console-connector-failures-session-termination/m-p/1409262#M5975</guid>
      <dc:creator>PY</dc:creator>
      <dc:date>2026-08-14T06:04:50Z</dc:date>
    </item>
  </channel>
</rss>

