F5 Logo MyF5
Search
  1. MyF5 Home
  2. Knowledge Centers
  3. BIG-IP APM
  4. BIG-IP Access Policy Manager: Portal Access
  5. Configuring Virtual Servers for Portal Access
Manual Chapter : Configuring Virtual Servers for Portal Access

Applies To:

Show Versions Show Versions

BIG-IP APM

  • 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Manual Chapter
Table of Contents | << Previous Chapter | Next Chapter >>

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.
Important: For portal access, specify that the virtual server is a host virtual server, and not a network virtual server.
  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 setting, select Host and in the Address field, type the IP address for the virtual server.
  4. From the HTTP Profile list, select http.
  5. In the Access Policy area, from the Access Profile list, select the access profile.
  6. To use GZIP compression with a portal access resource, from the HTTP Compression Profile list, select httpcompression.
  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 rewrite 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 serverssl-apm.
  11. If you want to provide connections to VDI desktop resources or Java RDP clients for Application Access, or allow Java rewriting for Portal Access, select the VDI & Java Support check box. You must enable this setting to make socket connections from a patched Java applet. If your applet doesn't 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 Update.
Your access policy is now associated with the virtual server.
Table of Contents | << Previous Chapter | Next Chapter >>
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5 Networks, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information