Configuring Remote Session Host

The remote session host component can be used to route browser-based session in a multi-site environment. Using this proxy you can build distributed environment with centralized authentication and de-centralized session management. In a multi-site environment, users can initiate session closer to the server and reduce latency issues.

• 124452903

• 124452903

Before you begin

• You have already installed the Sectona Web Access or Remote Session Host component. Refer to 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 Remote Session Proxy is installed.

• Port No: 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 segment to use 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 provides a list of 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 Hostname field for %ApplicationNodeHost% and thus provide dynamic Application Node URL.

• Availability Check: Enable this option if you have multiple proxies configured to access the target asset environment. This enables internal load balancing and reachability check before the connection is initiated.