previous
next
In addition to Assign Access (used in Step 5), Reflection for the Web provides several options to secure user access to your host applications.
Reflection for the Web supports many types of authentication. Each type is described in the Help topic: Configure Settings > Authentication & Authorization.
In the Administrative Console, click Configure Settings > General Security. You can set options for server access, passwords, smart card libraries, and cryptography settings. Click Help for information about the available options.
By default, Reflection for the Web enables web browsers to use the HTTP protocol to communicate between the client computer and the administrative server. Although HTTP is universally available to web browsers, it is not a secure protocol.
To secure the communication between the client and the web server, you can require web browsers to use the HTTPS protocol (which provides TLS/SSL encryption) when connecting to the Administrative Server. For more information, open the Administrative Console Help to Technical References > Security Overview.
Reflection for the Web provides support for TLS 1.2. For more information, see the Technical References -- Security Overview and Using the Security Proxy. You can also search for other Help topics about using TLS.
The Security Proxy can be used to encrypt the data between the client and the Security Proxy. You can install the security proxy when you run the automated installer, and it can be installed on a different machine.
The Security Proxy is managed by Host Access Management and Security Server. For more information, see Using the Security Proxy Server.