Applies To:
Show VersionsBIG-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
Overview: Configuring APM for web access management
Access Policy Manager (APM) web access management provides the ability to access web applications through a web browser without the use of tunnels or specific resources. With this type of access, APM communicates with backend web servers, forwarding requests from the client to web servers within a local traffic pool.
In a typical web access management connection, access occurs through a rewriting engine that rewrites links and URLs to and from the client. APM web access management eliminates the need for content rewriting, allowing access to the configured local traffic pool after the user passes through the access policy checks.
Task summary
To support APM web access management connections, you need a pool of web application servers, an access profile and access policy, and a virtual server.
About configuring timeout for a web access management session
The web access management access type does not have a logout mechanism, so you must configure a timeout option from these choices.
- The Windows Cache and Session Control access policy item
- Terminates a user session when it detects that the browser screen has closed. You can also configure it to provide inactivity timeouts for the user session using the Terminate session on user inactivity setting.
- Maximum Session Timeout access profile setting
- Provides an absolute limit for the duration of the access policy connection, regardless of user activity. To ensure that a user session closes after a certain number of seconds, configure this setting.
- Inactivity Timeout access profile setting
- Terminates the session after there is no traffic flow for a specified number of seconds.
Note: Depending on the application, you might not want to set this to a very short duration, because many applications cache user typing and generate no traffic for an extended period. In this scenario, a session can time out while the application is still in use, but the content of the user input is not relayed back to the server..