Applies To:Show Versions
- 13.0.1, 13.0.0
Overview: What is portal access?
Portal access allows end users access to internal web applications with a web browser from outside the network. With portal access, the BIG-IP® Access Policy Manager® communicates with back-end servers, and rewrites links in application web pages so that further requests from the client browser are directed back to the Access Policy Manager server. With portal access, the client computer requires no specialized client software other than a web browser.
Portal access provides clients with secure access to internal web servers, such as Microsoft OutlookWeb Access (OWA), Microsoft SharePoint, and IBM Domino Web Access. Using portal access functionality, you can also provide access to most web-based applications and internal web servers.
Portal access differs from network access, which provides direct access from the client to the internal network. Network access does not manipulate or analyze the content being passed between the client and the internal network. The portal access configuration gives the administrator both refined control over the applications that a user can access through Access Policy Manager, and content inspection for the application data. The other advantage of portal access is security. Even if a workstation might not meet requirements for security for full network access, such a workstation can be passed by the access policy to certain required web applications, without allowing full network access. In a portal access policy, the client computer itself never communicates directly with the end-point application. That means that all communication is inspected at a very high level, and any attacks originating on the client computer fail because the attack cannot navigate through the links that have been rewritten by the portal access engine.
About portal access configuration elements
A portal access configuration requires several elements:
- A portal access resource including one or more portal access resource items
- An access profile
- An access policy that assigns both:
- A portal access resource
- A portal access or full webtop
- A rewrite profile (you can use the default rewrite profile)
- A connectivity profile
- A virtual server that assigns the access profile and a rewrite profile
Portal access elements are summarized in this diagram.
Portal access elements
Understanding portal access patching
Understanding full patching mode
In full patching mode, you can select one or more of the following content types in which portal access rewrites links.
|Patching content type
|Rewrites links in HTML content to redirect to the Access Policy Manager®.
|Rewrites links to CSS files, and within CSS content, to redirect to the Access Policy Manager.
|Rewrites links in Flash movies and objects to redirect requests to the Access Policy Manager.
|Rewrites link content in Java code to redirect requests to the Access Policy Manager. Access Policy Manager can also relay and handle any socket connections required by a patched Java applet.
Understanding minimal patching mode
In minimal patching mode, portal access allows only minimum rewriting of web application content. Minimal patching mode is useful for troubleshooting, or when full portal access patching fails with a file or site.
In minimal patching mode, only HTML and CSS content is patched.
To use minimal patching, the following conditions must be met:
- You must create a local traffic pool for the application server or servers, and select it as the default pool in the virtual server definition.
- You must add a portal access resource item to the portal access resource, and configure it with host *, and port 0 (or any). In addition, the path /* must be specified in the resource item.
- You must configure the scheme any, not http or https.
- Minimal patching does not use a webtop, and will fail if one is assigned. For this reason, you must disable the Publish on webtop option, and you can not assign a webtop to the minimal patching access policy branch.
|Specifies a method of patching that replaces all HTTP scheme addresses with HTTPS scheme addresses.
|Specifies a method of patching where one or multiple hosts (typically the actual application server host name) are replaced with another host, the Access Policy Manager® virtual server. You can specify multiple hosts separated with spaces for host search strings. The host replace string must be the Access Policy Manager virtual server IP address or fully qualified domain name (FQDN).
Additional resources and documentation for BIG-IP Access Policy Manager
You can access all of the following BIG-IP® system documentation from the AskF5™ Knowledge Base located at http://support.f5.com/.
|BIG-IP® Access Policy Manager®: Application Access
|This guide contains information for an administrator to configure application tunnels for secure, application-level TCP/IP connections from the client to the network.
|BIG-IP® Access Policy Manager®: Authentication and Single-Sign On
|This guide contains information to help an administrator configure APM for single sign-on and for various types of authentication, such as AAA server, SAML, certificate inspection, local user database, and so on.
|BIG-IP® Access Policy Manager®: Customization
|This guide provides information about using the APM customization tool to provide users with a personalized experience for access policy screens, and errors. An administrator can apply your organization's brand images and colors, change messages and errors for local languages, and change the layout of user pages and screens.
|BIG-IP® Access Policy Manager®: Edge Client and Application Configuration
|This guide contains information for an administrator to configure the BIG-IP® system for browser-based access with the web client as well as for access using BIG-IP Edge Client® and BIG-IP Edge Apps. It also includes information about how to configure or obtain client packages and install them for BIG-IP Edge Client for Windows, Mac, and Linux, and Edge Client command-line interface for Linux.
|BIG-IP® Access Policy Manager®: Implementations
|This guide contains implementations for synchronizing access policies across BIG-IP systems, hosting content on a BIG-IP system, maintaining OPSWAT libraries, configuring dynamic ACLs, web access management, and configuring an access policy for routing.
|BIG-IP® Access Policy Manager®: Network Access
|This guide contains information for an administrator to configure APM Network Access to provide secure access to corporate applications and data using a standard web browser.
|BIG-IP® Access Policy Manager®: Portal Access
|This guide contains information about how to configure APM Portal Access. In Portal Access, APM communicates with back-end servers, rewrites links in application web pages, and directs additional requests from clients back to APM.
|BIG-IP® Access Policy Manager®: Secure Web Gateway
|This guide contains information to help an administrator configure Secure Web Gateway (SWG) explicit or transparent forward proxy and apply URL categorization and filtering to Internet traffic from your enterprise.
|BIG-IP® Access Policy Manager®: Third-Party Integration
|This guide contains information about integrating third-party products with Access Policy Manager (APM®). It includes implementations for integration with VMware Horizon View, Oracle Access Manager, Citrix Web Interface site, and so on.
|BIG-IP® Access Policy Manager®: Visual Policy Editor
|This guide contains information about how to use the visual policy editor to configure access policies.
|Release notes contain information about the current software release, including a list of associated documentation, a summary of new features, enhancements, fixes, known issues, and available workarounds.
|Solutions and Tech Notes
|Solutions are responses and resolutions to known issues. Tech Notes provide additional configuration instructions and how-to information.