Manual Chapter : Implementing APM System Authentication

Applies To:

Show Versions Show Versions

BIG-IP DNS

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP Analytics

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP AFM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP PEM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP ASM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP AAM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP APM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0

BIG-IP LTM

  • 14.1.2, 14.1.0, 14.0.1, 14.0.0
Manual Chapter

Implementing APM System Authentication

Overview: Configuring authentication for a remote system based on APM

As an administrator in a large computing environment, you might prefer to store user accounts remotely, on a dedicated authentication server. When you want to use a remote server to authenticate traffic that manages a BIG-IP® system, you can store BIG-IP system administrative accounts on an AAA server. BIG-IP APM® supports AAA servers such as HTTP, LDAP, RADIUS, Active Directory, and TACACS+. To complete the authentication process, you must add the newly configured AAA action to an access policy. You can find more information about AAA authentication and access policies in
BIG-IP Access Policy Manager: Authentication and Single Sign-On
and
BIG-IP Access Policy Manager: Visual Policy Editor
.
System authentication using APM methods will not work if the user name and password contains Unicode characters (for example, Chinese characters) or the symbols ampersand (
&
), colon (
:
), less than (
<
), and apostrophe (
'
).

Creating a user authentication based on APM

Before you begin:
  • Verify that the BIG-IP system user accounts have been created on the remote authentication server.
  • Verify that the appropriate user groups, if any, are defined on the remote authentication server.
You can configure the BIG-IP system to use an APM server for authenticating BIG-IP system user accounts, that is, traffic that passes through the management interface (MGMT).
  1. On the Main tab, click
    System
    Users
    .
  2. On the menu bar, click
    Authentication
    .
  3. Click
    Change
    .
  4. From the
    User Directory
    list, select
    Remote - APM Based
    .
  5. For the
    Access Profile
    setting, click the
    +
    button.
    The screen refreshes to show general properties.
  6. In the
    Name
    field, type a name for the access profile.
    A access profile name must be unique among all access profile and any per-request policy names.
  7. From the
    Default Language
    list, select a language.
    The default is
    English (en)
    .
  8. From the
    Authentication Type
    list, select the type of authentication for the APM based remote user authentication.
    The screen refreshes to show areas and settings specific to the authentication type.
  9. Fill in the fields.
  10. Click
    Finished
    .
You can now authenticate administrative traffic for user accounts that are stored on a remote APM server. If you have no need to configure group-based user authorization, your configuration tasks are complete.

Example access policy using APM LDAP authentication

This is an example of an access policy with all the associated elements that are needed to authenticate and authorize your users with LDAP authentication.
Example of an access policy for LDAP Auth
Example of an access policy for LDAP auth