<?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 SIA Queries in Idira General Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/idira-general-discussions/sia-queries/m-p/1404438#M546</link>
    <description>&lt;P&gt;1. How can we view detailed connection information for HTML5 sessions routed through SIA? The Session Diagnostics tab on the portal does not provide full details for the target server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. The SIA portal was recently installed, and we noticed that the TLS certificates tab already has certificates uploaded. Were these certificates uploaded automatically? the same ones used on the legacy HTML5 system?&lt;/P&gt;</description>
    <pubDate>Tue, 02 Sep 2025 09:53:46 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-09-02T09:53:46Z</dc:date>
    <item>
      <title>SIA Queries</title>
      <link>https://live.paloaltonetworks.com/t5/idira-general-discussions/sia-queries/m-p/1404438#M546</link>
      <description>&lt;P&gt;1. How can we view detailed connection information for HTML5 sessions routed through SIA? The Session Diagnostics tab on the portal does not provide full details for the target server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. The SIA portal was recently installed, and we noticed that the TLS certificates tab already has certificates uploaded. Were these certificates uploaded automatically? the same ones used on the legacy HTML5 system?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 09:53:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/idira-general-discussions/sia-queries/m-p/1404438#M546</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-09-02T09:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: SIA Queries</title>
      <link>https://live.paloaltonetworks.com/t5/idira-general-discussions/sia-queries/m-p/1404439#M547</link>
      <description>&lt;UL&gt;&lt;LI&gt;HTML5GW sessions are&amp;nbsp;not counted&amp;nbsp;in the SIA Connectors page by default.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;LI&gt;The diagnostics may only reflect&amp;nbsp;SIA tunnel status, not the full&amp;nbsp;PSM path&amp;nbsp;or&amp;nbsp;target resolution.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;LI&gt;If the&amp;nbsp;network identifier&amp;nbsp;(e.g. “ON-PREMISE”) is missing or misconfigured in the Connector Pool, SIA may fail to route traffic correctly.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Ensure that the&amp;nbsp;HTML5GW service&amp;nbsp;is properly integrated with SIA:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Use the&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;connectViaBrowser&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;parameter in the&amp;nbsp;DPA Configuration Service:&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;JSON&lt;/LI&gt;&lt;LI&gt;PATCH /api/settings&lt;/LI&gt;&lt;LI&gt;{&lt;/LI&gt;&lt;LI&gt;  "connectViaBrowser": { "enabled": true }&lt;/LI&gt;&lt;LI&gt;}&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;This enables the “Connect via Browser” button and ensures HTML5GW sessions are tracked.&lt;/LI&gt;&lt;LI&gt;Connect with SIA via HTML5GW&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;2.&amp;nbsp;Use FQDNs Instead of IPs&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;HTML5GW sessions require&amp;nbsp;FQDNs&amp;nbsp;for target servers to match SSL certificates and connector pool identifiers.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;LI&gt;If IPs are used, diagnostics may fail or show incomplete data.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;3.&amp;nbsp;Check Connector Pool Configuration&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Ensure that the&amp;nbsp;Connector Pool&amp;nbsp;includes the correct&amp;nbsp;network identifiers&amp;nbsp;and&amp;nbsp;FQDNs&amp;nbsp;for the PSM targets.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The&amp;nbsp;TLS certificates tab&amp;nbsp;in the SIA portal does not automatically import certificates from the legacy HTML5 system. Instead:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Certificates must be&amp;nbsp;manually uploaded&amp;nbsp;via the TLS Certificates page in the SIA portal.&lt;/LI&gt;&lt;LI&gt;Once uploaded, they are available for use across all target sets.&lt;/LI&gt;&lt;LI&gt;If&amp;nbsp;“Verify with certificate”&amp;nbsp;is enabled (which it is by default), SIA will attempt to connect using all available certificates until a match is found.&lt;/LI&gt;&lt;LI&gt;Manage certificates&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This means that if certificates are already present in your portal, they were either:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Uploaded manually during setup.&lt;/LI&gt;&lt;LI&gt;Included as part of a&amp;nbsp;preconfigured deployment bundle&amp;nbsp;(e.g. from a template or automation script).&lt;/LI&gt;&lt;LI&gt;Possibly reused from previous HTML5GW configurations if the same certificate files were manually added&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If diagnostics show “No active connector found for network: ON-PREMISE,” create a dummy network to force routing.&lt;/LI&gt;&lt;LI&gt;SIA (formerly DPA) Enablement POD&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 13:19:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/idira-general-discussions/sia-queries/m-p/1404439#M547</guid>
      <dc:creator>RobertS_Cyberark</dc:creator>
      <dc:date>2025-09-02T13:19:09Z</dc:date>
    </item>
  </channel>
</rss>

