SIA Queries

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

SIA Queries

L3 Networker

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.

 

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?

1 accepted solution

Accepted Solutions

L7 Applicator
  • HTML5GW sessions are not counted in the SIA Connectors page by default.
  • SIA (formerly DPA) Enablement POD
  • The diagnostics may only reflect SIA tunnel status, not the full PSM path or target resolution.
  • SIA (formerly DPA) Enablement POD
  • If the network identifier (e.g. “ON-PREMISE”) is missing or misconfigured in the Connector Pool, SIA may fail to route traffic correctly.
  • SIA (formerly DPA) Enablement POD

Ensure that the HTML5GW service is properly integrated with SIA:

  • Use the 
  • connectViaBrowser
  •  
  •  parameter in the DPA Configuration Service:
  •  
  •  
  •  
  •  
  •  
  •  
  • JSON
  • PATCH /api/settings
  • {
  • "connectViaBrowser": { "enabled": true }
  • }
  •  
  • This enables the “Connect via Browser” button and ensures HTML5GW sessions are tracked.
  • Connect with SIA via HTML5GW

2. Use FQDNs Instead of IPs

  • HTML5GW sessions require FQDNs for target servers to match SSL certificates and connector pool identifiers.
  • SIA (formerly DPA) Enablement POD
  • If IPs are used, diagnostics may fail or show incomplete data.

3. Check Connector Pool Configuration

  • Ensure that the Connector Pool includes the correct network identifiers and FQDNs for the PSM targets.
  • SIA (formerly DPA) Enablement POD

 

 

 

The TLS certificates tab in the SIA portal does not automatically import certificates from the legacy HTML5 system. Instead:

  • Certificates must be manually uploaded via the TLS Certificates page in the SIA portal.
  • Once uploaded, they are available for use across all target sets.
  • If “Verify with certificate” is enabled (which it is by default), SIA will attempt to connect using all available certificates until a match is found.
  • Manage certificates

 

This means that if certificates are already present in your portal, they were either:

  • Uploaded manually during setup.
  • Included as part of a preconfigured deployment bundle (e.g. from a template or automation script).
  • Possibly reused from previous HTML5GW configurations if the same certificate files were manually added

 

 

 

 

  • If diagnostics show “No active connector found for network: ON-PREMISE,” create a dummy network to force routing.
  • SIA (formerly DPA) Enablement POD

 

 

View solution in original post

1 REPLY 1

L7 Applicator
  • HTML5GW sessions are not counted in the SIA Connectors page by default.
  • SIA (formerly DPA) Enablement POD
  • The diagnostics may only reflect SIA tunnel status, not the full PSM path or target resolution.
  • SIA (formerly DPA) Enablement POD
  • If the network identifier (e.g. “ON-PREMISE”) is missing or misconfigured in the Connector Pool, SIA may fail to route traffic correctly.
  • SIA (formerly DPA) Enablement POD

Ensure that the HTML5GW service is properly integrated with SIA:

  • Use the 
  • connectViaBrowser
  •  
  •  parameter in the DPA Configuration Service:
  •  
  •  
  •  
  •  
  •  
  •  
  • JSON
  • PATCH /api/settings
  • {
  • "connectViaBrowser": { "enabled": true }
  • }
  •  
  • This enables the “Connect via Browser” button and ensures HTML5GW sessions are tracked.
  • Connect with SIA via HTML5GW

2. Use FQDNs Instead of IPs

  • HTML5GW sessions require FQDNs for target servers to match SSL certificates and connector pool identifiers.
  • SIA (formerly DPA) Enablement POD
  • If IPs are used, diagnostics may fail or show incomplete data.

3. Check Connector Pool Configuration

  • Ensure that the Connector Pool includes the correct network identifiers and FQDNs for the PSM targets.
  • SIA (formerly DPA) Enablement POD

 

 

 

The TLS certificates tab in the SIA portal does not automatically import certificates from the legacy HTML5 system. Instead:

  • Certificates must be manually uploaded via the TLS Certificates page in the SIA portal.
  • Once uploaded, they are available for use across all target sets.
  • If “Verify with certificate” is enabled (which it is by default), SIA will attempt to connect using all available certificates until a match is found.
  • Manage certificates

 

This means that if certificates are already present in your portal, they were either:

  • Uploaded manually during setup.
  • Included as part of a preconfigured deployment bundle (e.g. from a template or automation script).
  • Possibly reused from previous HTML5GW configurations if the same certificate files were manually added

 

 

 

 

  • If diagnostics show “No active connector found for network: ON-PREMISE,” create a dummy network to force routing.
  • SIA (formerly DPA) Enablement POD

 

 

  • 1 accepted solution
  • 197 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!