Manual Chapter : Configuring Virtual Servers for Portal Access
Applies To:Show Versions
- 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0
Configuring Virtual Servers for Portal Access
Defining a virtual server for portal access
You associate an access policy and a rewrite profile with the virtual server, to allow portal access in an access policy.
For portal access, a virtual server for an access policy, specify an IP address for a single host as the destination address.
- On the Main tab, click.The Virtual Server List screen opens.
- Click the name of the virtual server you want to modify.
- For theDestination Address/Masksetting, confirm that theHostbutton is selected, and type the IP address in CIDR format.The supported format is address/prefix, where the prefix length is in bits. For example, an IPv4 address/prefix is10.0.0.1or10.0.0.0/24, and an IPv6 address/prefix isffe1::0020/64or2001:ed8:77b5:2:10:10:100:42/64. When you use an IPv4 address without specifying a prefix, the BIG-IP system automatically uses a/32prefix.The IP address you type must be available and not in the loopback network.
- From theHTTP Profile (Client)list, select a previously-created HTTP/2 profile for client-side traffic.
- In the Access Policy area, from theAccess Profilelist, select the access profile that you configured earlier.
- To use GZIP compression with a portal access resource, from theHTTP Compression Profilelist, selecthttpcompression.
- If you are using a connectivity profile, from theConnectivity Profilelist, select the connectivity profile.
- If you are creating a virtual server to use with portal access resources in addition to remote desktops, from theRewrite Profilelist, select the defaultrewriteprofile, or another rewrite profile you created.
- If you use client SSL for this profile, from theSSL Profile (Client)list, select a client SSL profile.
- If you are using HTTPS with any portal access pages, from theSSL Profile (Server)list, selectserverssl-apm.
- If you want to provide connections to allow Java rewriting for portal access or support a per-app VPN connection that is configured on a mobile device, select theApplication Tunnels (Java & Per-App VPN)check box.You must enable this setting to make socket connections from a patched Java applet. If your applet does not require socket connections, or only uses HTTP to request resources, this setting is not required.
- If you want to provide native integration with an OAM server for authentication and authorization, select theOAM Supportcheck box.You must have an OAM server configured in order to enable OAM support.
Your access policy is now associated with the virtual server.