<?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>article How the new HTML5 Gateway works in Remote Access Articles</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-articles/how-the-new-html5-gateway-works/ta-p/1427570</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;What is the connection flow for the new HTML5 Gateway&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/99833iB39374B2401AC1BC/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png" alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Step-by-Step Connection Sequence&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;Remote User Accesses the Privilege Cloud Portal&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Employee or vendor opens a browser and navigates to the Privilege Cloud Portal (e.g., https://&amp;lt;your-subdomain&amp;gt;.privilegecloud.cyberark.com or similar ISPSS portal URL).&lt;/LI&gt;&lt;LI&gt;Authenticates (SSO, MFA, etc.).&lt;/LI&gt;&lt;LI&gt;This establishes a session cookie used for all subsequent authorized requests.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;User Selects a Target Account and Initiates Connection&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;In the portal (Accounts / My Accounts view), the user selects a privileged account/target configured for HTML5 access.&lt;/LI&gt;&lt;LI&gt;Clicks Connect (or chooses the HTML5/browser option if multiple protocols are available).&lt;/LI&gt;&lt;LI&gt;The portal checks SIA/HTML5 capability (via settings and platform configuration, e.g., AllowSelectHTML5 = Yes on the PSM connector/platform).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Portal Prepares Connection Metadata&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;The portal fetches account details from the vault (credentials are not sent in clear text).&lt;/LI&gt;&lt;LI&gt;Determines PSM server details, target hostname/IP, port (usually 3389 for RDP), username format (e.g., secureaccess\...), SSO/alternate shell indicator (e.g., /sso).&lt;/LI&gt;&lt;LI&gt;Builds a human-readable title (e.g., target hostname).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Portal Sends Authenticated Request to Cloud-Hosted HTML5 Gateway&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Constructs inner JSON payload (as seen in traces):&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/99832iF4FE962068F0CAC9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png" alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;OL start="4"&gt;&lt;UL&gt;&lt;LI&gt;Base64-encodes it → wraps in { "PSMGWRequest": "&amp;lt;base64&amp;gt;" }.&lt;/LI&gt;&lt;LI&gt;Sends HTTPS POST (port 443) to the regional HTML5 Gateway endpoint: https://&amp;lt;region&amp;gt;.webaccess.cyberark.cloud/guac/direct (e.g., us-east-1.webaccess.cyberark.cloud/guac/direct).&lt;/LI&gt;&lt;LI&gt;Includes the user's session Cookie for authorization (this is the key auth mechanism).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;HTML5 Gateway Authorizes and Processes the Request&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Validates the session cookie against Privilege Cloud identity backend.&lt;/LI&gt;&lt;LI&gt;Decodes the Base64 payload and recognizes "SIA-RDP" → knows this is an SIA-routed session.&lt;/LI&gt;&lt;LI&gt;Prepares to initiate a secure, browser-compatible session (using Apache Guacamole backend).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;HTML5 Gateway Requests Session Routing via SIA Backend&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Communicates (HTTPS/443) with the SIA service in the Privilege Cloud environment.&lt;/LI&gt;&lt;LI&gt;SIA selects an appropriate SIA Connector pool (based on configured PSM domains/FQDNs and network names).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;SIA Backend Communicates with On-Premises SIA/DPA Connector&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;The SIA Connector (installed in customer environment) maintains an outbound-only persistent tunnel to the SIA backend (HTTPS/443).&lt;/LI&gt;&lt;LI&gt;SIA backend instructs the connector to establish a session path to the correct PSM server.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;SIA Connector Forwards to PSM Server&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Connector opens outbound connection (typically TCP/3389) to the target PSM server (on-premises or in customer network).&lt;/LI&gt;&lt;LI&gt;PSM authenticates the request, retrieves/uses vaulted credentials (or just-in-time access), and connects to the target system (RDP/SSH/other protocol over the appropriate port).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Full Session Tunnel is Established (Bidirectional Proxying)&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;PSM proxies the protocol (RDP/SSH/etc.) to/from the target.&lt;/LI&gt;&lt;LI&gt;SIA Connector relays traffic securely back through the outbound tunnel to the SIA backend.&lt;/LI&gt;&lt;LI&gt;SIA backend forwards it to the HTML5 Gateway.&lt;/LI&gt;&lt;LI&gt;HTML5 Gateway translates the protocol into HTML5/WebSocket (wss:// over 443) for browser rendering.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Browser Renders the Interactive Session&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;After successful POST response (200 OK), the portal opens a new browser tab.&lt;/LI&gt;&lt;LI&gt;The tab connects via WebSocket to the HTML5 Gateway (e.g., wss://&amp;lt;region&amp;gt;.webaccess.cyberark.cloud/.../websocket-tunnel).&lt;/LI&gt;&lt;LI&gt;User sees and interacts with the target desktop/session directly in the browser (keyboard, mouse, clipboard, optional file transfer).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Session Lifecycle &amp;amp; Termination&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;PSM enforces recording, monitoring, auditing, and policies.&lt;/LI&gt;&lt;LI&gt;SIA ensures just-in-time access (no standing privileges).&lt;/LI&gt;&lt;LI&gt;Session ends when user closes the tab, disconnects, or timeout occurs → PSM terminates the target connection.&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;
&lt;P&gt;Alignment with the Diagram&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Red arrows/lines → Employee/vendor → Portal → HTML5 Gateway (browser flow via 443).&lt;/LI&gt;&lt;LI&gt;Blue lines → Outbound from Connector → PSM (3389) → Target.&lt;/LI&gt;&lt;LI&gt;Reverse proxy / HTTPS 443 → All cloud ↔ user and cloud ↔ connector communication.&lt;/LI&gt;&lt;LI&gt;DPA Connector → Acts as the secure bridge (reverse tunnel) between customer environment and cloud HTML5GW.&lt;/LI&gt;&lt;LI&gt;No direct inbound access from internet to customer PSM/targets.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Feb 2026 20:29:22 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-02-17T20:29:22Z</dc:date>
    <item>
      <title>How the new HTML5 Gateway works</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-articles/how-the-new-html5-gateway-works/ta-p/1427570</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;What is the connection flow for the new HTML5 Gateway&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/99833iB39374B2401AC1BC/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png" alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000iyJ3G.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Step-by-Step Connection Sequence&lt;/P&gt;
&lt;OL start="1"&gt;&lt;LI&gt;Remote User Accesses the Privilege Cloud Portal&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Employee or vendor opens a browser and navigates to the Privilege Cloud Portal (e.g., https://&amp;lt;your-subdomain&amp;gt;.privilegecloud.cyberark.com or similar ISPSS portal URL).&lt;/LI&gt;&lt;LI&gt;Authenticates (SSO, MFA, etc.).&lt;/LI&gt;&lt;LI&gt;This establishes a session cookie used for all subsequent authorized requests.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;User Selects a Target Account and Initiates Connection&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;In the portal (Accounts / My Accounts view), the user selects a privileged account/target configured for HTML5 access.&lt;/LI&gt;&lt;LI&gt;Clicks Connect (or chooses the HTML5/browser option if multiple protocols are available).&lt;/LI&gt;&lt;LI&gt;The portal checks SIA/HTML5 capability (via settings and platform configuration, e.g., AllowSelectHTML5 = Yes on the PSM connector/platform).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Portal Prepares Connection Metadata&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;The portal fetches account details from the vault (credentials are not sent in clear text).&lt;/LI&gt;&lt;LI&gt;Determines PSM server details, target hostname/IP, port (usually 3389 for RDP), username format (e.g., secureaccess\...), SSO/alternate shell indicator (e.g., /sso).&lt;/LI&gt;&lt;LI&gt;Builds a human-readable title (e.g., target hostname).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Portal Sends Authenticated Request to Cloud-Hosted HTML5 Gateway&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Constructs inner JSON payload (as seen in traces):&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/99832iF4FE962068F0CAC9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png" alt="ka3Vy00000BSJvpIAH__eid=ka3Vy00000BSJvp&amp;amp;feoid=00N2J000009R3kg&amp;amp;refid=0EMVy00000ixSrm.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;OL start="4"&gt;&lt;UL&gt;&lt;LI&gt;Base64-encodes it → wraps in { "PSMGWRequest": "&amp;lt;base64&amp;gt;" }.&lt;/LI&gt;&lt;LI&gt;Sends HTTPS POST (port 443) to the regional HTML5 Gateway endpoint: https://&amp;lt;region&amp;gt;.webaccess.cyberark.cloud/guac/direct (e.g., us-east-1.webaccess.cyberark.cloud/guac/direct).&lt;/LI&gt;&lt;LI&gt;Includes the user's session Cookie for authorization (this is the key auth mechanism).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;HTML5 Gateway Authorizes and Processes the Request&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Validates the session cookie against Privilege Cloud identity backend.&lt;/LI&gt;&lt;LI&gt;Decodes the Base64 payload and recognizes "SIA-RDP" → knows this is an SIA-routed session.&lt;/LI&gt;&lt;LI&gt;Prepares to initiate a secure, browser-compatible session (using Apache Guacamole backend).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;HTML5 Gateway Requests Session Routing via SIA Backend&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Communicates (HTTPS/443) with the SIA service in the Privilege Cloud environment.&lt;/LI&gt;&lt;LI&gt;SIA selects an appropriate SIA Connector pool (based on configured PSM domains/FQDNs and network names).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;SIA Backend Communicates with On-Premises SIA/DPA Connector&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;The SIA Connector (installed in customer environment) maintains an outbound-only persistent tunnel to the SIA backend (HTTPS/443).&lt;/LI&gt;&lt;LI&gt;SIA backend instructs the connector to establish a session path to the correct PSM server.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;SIA Connector Forwards to PSM Server&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;Connector opens outbound connection (typically TCP/3389) to the target PSM server (on-premises or in customer network).&lt;/LI&gt;&lt;LI&gt;PSM authenticates the request, retrieves/uses vaulted credentials (or just-in-time access), and connects to the target system (RDP/SSH/other protocol over the appropriate port).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Full Session Tunnel is Established (Bidirectional Proxying)&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;PSM proxies the protocol (RDP/SSH/etc.) to/from the target.&lt;/LI&gt;&lt;LI&gt;SIA Connector relays traffic securely back through the outbound tunnel to the SIA backend.&lt;/LI&gt;&lt;LI&gt;SIA backend forwards it to the HTML5 Gateway.&lt;/LI&gt;&lt;LI&gt;HTML5 Gateway translates the protocol into HTML5/WebSocket (wss:// over 443) for browser rendering.&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Browser Renders the Interactive Session&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;After successful POST response (200 OK), the portal opens a new browser tab.&lt;/LI&gt;&lt;LI&gt;The tab connects via WebSocket to the HTML5 Gateway (e.g., wss://&amp;lt;region&amp;gt;.webaccess.cyberark.cloud/.../websocket-tunnel).&lt;/LI&gt;&lt;LI&gt;User sees and interacts with the target desktop/session directly in the browser (keyboard, mouse, clipboard, optional file transfer).&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;Session Lifecycle &amp;amp; Termination&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;PSM enforces recording, monitoring, auditing, and policies.&lt;/LI&gt;&lt;LI&gt;SIA ensures just-in-time access (no standing privileges).&lt;/LI&gt;&lt;LI&gt;Session ends when user closes the tab, disconnects, or timeout occurs → PSM terminates the target connection.&lt;/LI&gt;&lt;/UL&gt;&lt;/OL&gt;
&lt;P&gt;Alignment with the Diagram&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;Red arrows/lines → Employee/vendor → Portal → HTML5 Gateway (browser flow via 443).&lt;/LI&gt;&lt;LI&gt;Blue lines → Outbound from Connector → PSM (3389) → Target.&lt;/LI&gt;&lt;LI&gt;Reverse proxy / HTTPS 443 → All cloud ↔ user and cloud ↔ connector communication.&lt;/LI&gt;&lt;LI&gt;DPA Connector → Acts as the secure bridge (reverse tunnel) between customer environment and cloud HTML5GW.&lt;/LI&gt;&lt;LI&gt;No direct inbound access from internet to customer PSM/targets.&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Feb 2026 20:29:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-articles/how-the-new-html5-gateway-works/ta-p/1427570</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-17T20:29:22Z</dc:date>
    </item>
  </channel>
</rss>

