Manual Chapter : Configuring Virtual Servers for Portal Access

Applies To:

Show Versions Show Versions


  • 17.1.0
Manual Chapter

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.
  1. On the Main tab, click
    Local Traffic
    Virtual Servers
    The Virtual Server List screen opens.
  2. Click the name of the virtual server you want to modify.
  3. For the
    Destination Address/Mask
    setting, confirm that the
    button 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 is
    , and an IPv6 address/prefix is
    . When you use an IPv4 address without specifying a prefix, the BIG-IP system automatically uses a
    The IP address you type must be available and not in the loopback network.
  4. From the
    HTTP Profile (Client)
    list, select a previously-created HTTP/2 profile for client-side traffic.
  5. In the Access Policy area, from the
    Access Profile
    list, select the access profile that you configured earlier.
  6. To use GZIP compression with a portal access resource, from the
    HTTP Compression Profile
    list, select
  7. If you are using a connectivity profile, from the
    Connectivity Profile
    list, select the connectivity profile.
  8. If you are creating a virtual server to use with portal access resources in addition to remote desktops, from the
    Rewrite Profile
    list, select the default
    profile, or another rewrite profile you created.
  9. If you use client SSL for this profile, from the
    SSL Profile (Client)
    list, select a client SSL profile.
  10. If you are using HTTPS with any portal access pages, from the
    SSL Profile (Server)
    list, select
  11. 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 the
    Application 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.
  12. If you want to provide native integration with an OAM server for authentication and authorization, select the
    OAM Support
    check box.
    You must have an OAM server configured in order to enable OAM support.
  13. Click
Your access policy is now associated with the virtual server.