The remote session host component can route browser-based sessions in a multi-site environment. Using this proxy, you can build distributed environment with centralized authentication and de-centralized session management. Users can initiate sessions closer to the server in a multi-site environment and reduce latency issues.
Before you begin
-
You have already installed the Sectona Web Access or Remote Session Host component. Refer to the Installation Section for more details.
-
Ensure the PAM server can communicate with the remote session host as per communication the requirement mentioned in Standard Port Requirement for Installation.
Using Remote Session Host on external node
-
Navigate to System → Landing & Proxy Server.
-
Select Add New → Remote Session Host.
-
Provide a proxy reference name like RSH-SiteName.
-
Provide the Hostname and IP Address of the server where the Remote Session Proxy is installed.
-
Port No: The default port is 10443 unless you have customized it.
-
IP Segment / Location: If you wish to route all traffic from local machines to target assets with this session proxy, set it to All Asset. You can select specific locations / IP segments to use a specific session proxy.
-
Instances: Select applicable instances for this proxy configuration.
-
Log Server: Specify the location of the node where logs generated by accessing through should be stored. The system lists all configured nodes (HA / DR / Remote Sites) to be selected.
-
Application Node URL: This is auto-filled from the system as "https://%ApplicationNodeHost%:443". The system takes the value from the Hostname field for %ApplicationNodeHost% and thus provides a dynamic Application Node URL.
-
Availability Check: Enable this option if multiple proxies are configured to access the target asset environment. This enables internal load balancing and reachability checks before the connection is initiated.