![]() Remote users that use HTTP are automatically redirected to the portal using HTTPS. FQDN that resolves to the IP address of the Security Gateway.Remote users access the portal from a Web browser with where is one of these: Remote users log in to the portal using an authentication scheme configured for that Security Gateway. In the Fields column, select the minimum and maximum TLS version values in these fields:Įach Mobile Access-enabled Security Gateway leads to its own Mobile Access user portal.In the Objects column, select general_confs_obj.In GuiDBedit Tool, on the Tables tab, select Other > ssl_inspection.To Configure TLS Protocol Support for HTTPS inspection: On the Portal Properties page, set minimum and maximum versions for SSL and TLS protocols.In the Advanced Configuration section, click Configure.In SmartDashboard, open Global Properties > SmartDashboard Customization.To configure TLS protocol support for portals: Support for TLS 1.1 and TLS 1.2 is enabled by default but can be disabled in SmartDashboard (for web-based portals) or GuiDBedit Tool (see sk13009) (for HTTPS Inspection). In addition to SSLv3 and TLS 1.0 (RFC 2246), the Security Gateway supports: ![]() These portals (and HTTPS inspection) support the latest versions of the TLS protocol. The Security Gateway runs different web-based portals over HTTPS:Īll of these portals can resolve HTTPS hosts to IPv4 and IPv6 addresses over port 443. The Mobile Access Portal In This Section:
0 Comments
Leave a Reply. |