In the BIG-IP® Access Policy Manager®, an access profile is the profile that you select in a virtual server definition to establish a secured session. You can also configure an access profile to provide access control and security features to a local traffic virtual server hosting web applications.
The access profile contains:
Define an access policy for network access in order to provide access control conditions that you want users to satisfy, before they can connect to internal resources. For a network access policy, you need to configure a minimum of a resource assign action that assigns a network access resource.
You can configure the following settings in an access profile.
|Setting||Value||Description and defaults|
|Name||Specifies the name of the access profile.|
|Inactivity Timeout||Number of seconds, or 0||Specifies the inactivity timeout for the connection. If there is no activity between the client and server within the specified threshold time, the system closes the current session. By default, the threshold is 0, which specifies that as long as a connection is established, the inactivity timeout is inactive. However, if an inactivity timeout value is set, when server traffic exceeds the specified threshold, the inactivity timeout is reset.|
|Access Policy Timeout||Number of seconds, or 0||Designed to keep malicious users from creating a denial-of-service (DoS) attack on your server. The timeout requires that a user, who has followed through on a redirect, must reach the webtop before the timeout expires. The default value is 300 seconds.|
|Maximum Session Timeout||Number of seconds, or 0||The maximum lifetime is from the time a session is created, to when the session terminates. By default, it is set to 0, which means no limit. When you configure a maximum session timeout setting other than 0, there is no way to extend the session lifetime, and the user must log out and then log back in to the server when the session expires.|
|Max Concurrent Users||Number of users, or 0||The number of sessions allowed at one time for this access profile. The default value is 0 which specifies unlimited sessions.|
|Max Sessions Per User||Number between 1 and 1000, or 0||Specifies the number of sessions for one user that can be active concurrently. The default value is 0, which specifies unlimited sessions. You can set a limit from 1-1000. Values higher than 1000 cause the access profile to fail.|
|Logout URI Include||One or more URIs||Specifies a list of URIs to include in the access profile to initiate session logout.|
|Logout URI Timeout||Logout delay URI in seconds||Specifies the time delay before the logout occurs, using the logout URIs defined in the logout URI include list.|
|Domain Mode||Single Domain or Multiple Domains||Select Single Domain to apply your SSO configuration to a
single domain. Select Multiple Domain to apply your SSO configuration
across multiple domains. This is useful in cases where you want to allow your users a single
APM login session and apply it across multiple Local Traffic Manager™ or
Access Policy Manager® virtual servers, front-ending different domains.
Important: All virtual servers must be on one single BIG-IP system in order to apply SSO configurations across multiple domains.
|Primary Authentication URI||URI||The URI of your primary authentication server, for example https://logon.siterequest.com. This is required if you use SSO across multiple domains. You provide this URI so your users can access multiple back-end applications from multiple domains and hosts without requiring them to re-enter their credentials, because the user session is stored on the primary domain.|
|Cookie Options: Secure||Enable or disable check box||Enabled, this setting specifies to add the secure keyword to the session cookie. If you are configuring an application access control scenario where you are using an HTTPS virtual server to authenticate the user, and then sending the user to an existing HTTP virtual server to use applications, clear this check box.|
|Cookie Options: Persistent||Enable or disable check box||Enabled, this setting specifies to set cookies if the session does not have a webtop.
When the session is first established, session cookies are not marked as persistent, but when
the first response is sent to the client after the access policy completes successfully, the
cookies are marked persistent.
Note: Persistent cookies are updated for the expiration timeout every 60 seconds. The timeout is equal to the session inactivity timeout. If the session inactivity timeout is overwritten in the access policy, the overwritten value is used to set the persistent cookie expiration.
|SSO Configuration||Predefined SSO configuration||SSO configurations contain settings to configure single sign-on with an access profile. Select the SSO configuration from the list that you want applied to your domain.|
|Domain Cookie||A domain cookie||If you specify a domain cookie, then the line domain=specified_domain is added to the MRHsession cookie.|
|Configure Authentication Domains||Multiple||If you specify multiple domains, populate this area with hosts or domains. Each host or domain can have a separate SSO config, and you can set persistent or secure cookies. Click Add to add each host you configure.|
|Accepted Languages||Language strings||Adds a built-in or customized language to the list of accepted languages. Accepted languages can be customized separately and can present customized messages and screens to users, if the user's default browser language is one of the accepted languages. Select a language from the Factory Builtin Languages list and click the Move button (<<) to add it to the Accepted Languages list. Select a language from the Additional Languages list and click Add to add it to the Accepted Languages list.|
|Factory Builtin Languages||Languages in a predefined list||Lists the predefined languages on the Access Policy Manager system, which can be added to the Accepted Languages list. Predefined languages include customized messages and fields for common appearance items, as opposed to Additional Languages, which must be separately customized.|
|Additional Languages||Languages in a predefined list||Lists additional languages that can be added to the Accepted Languages list, and customized on the Access Policy Manager system. These languages are populated with English messages and fields and must be individually customized using the Customization menu, as opposed to Factory Builtin Languages, which are already customized.|
|Resource Assign||Select the Resource Assign action to add a network access resource only. Resource Assign does not allow you to add a webtop or ACLs. If you want to add ACLs, a webtop, or webtop links after you add a Resource Assign action, you can add them with the individual actions ACL Assign and Webtop and Links Assign.|
|Full Resource Assign||Select the Full Resource Assign action to add a network access resource, and optionally add a webtop, webtop links, and one or more ACLs.|