Applies To:

Show Versions Show Versions

Manual Chapter: BIG-IP User Accounts
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

13 
An important part of managing the BIG-IP® system is creating and managing user accounts for BIG-IP system administrators. By creating user accounts for system administrators, you provide additional layers of security. User accounts ensure that the system:
To enable user authentication and authorization, you assign passwords and user roles to your user accounts. Passwords allow you to authenticate your users when they attempt to log in to the BIG-IP system. User roles allow you to control user access to BIG-IP system resources.
You can create and store your BIG-IP administrative accounts either locally on the BIG-IP system, or remotely on a separate authentication server. If you want your user accounts to reside locally on the BIG-IP system, you create those user accounts on the BIG-IP system and assign user roles to them.
If you want your user accounts to reside remotely on a separate authentication server, you do not use the BIG-IP system to create the accounts. Instead, you use the mechanism provided by the server vendor, and you use the BIG-IP system strictly to assign user roles to those remote accounts and to maintain those user role assignments over time. The types of servers that you can use to remotely store BIG-IP system user accounts are:
To manage user accounts, including user roles, on the BIG-IP system, log in to the BIG-IP Configuration utility, and on the Main tab, expand System, and click Users.
Important: For information on managing remote user accounts, see Managing remote user accounts, and the guide titled BIG-IP® Local Traffic Manager: Implementations.
There are two types of user accounts on the BIG-IP system: The system maintenance account and a set of standard user accounts.
The system maintenance account
The system maintenance account is a user account that you maintain using the Setup utility. The name of the system maintenance account is root. This account resides locally on the BIG-IP system and grants full access to BIG-IP system resources. You configure and maintain this account using the Setup utility and the Configuration utility, respectively.
Standard user accounts
Standard user accounts are user accounts that you create for other BIG-IP system administrators to use. Standard user accounts can reside either locally on the BIG-IP system, or remotely on a remote authentication server. You create and maintain these accounts using the browser-based Configuration utility or the command line interface. Creating standard user accounts allows you to assign various user roles to those accounts as a way to control system administrator access to BIG-IP system resources. A special standard user account is the admin account, which automatically exists on any BIG-IP system. For more information on the admin account, see Configuring the admin account. For more information on user roles, see Understanding user roles.
Note: Excluding the admin account, the entire set of standard user accounts that you create for BIG-IP system administrators must reside either locally on the BIG-IP system, or remotely on another type of authentication server.
You are not required to have any user accounts other than the root and admin accounts, but F5 Networks® recommends that you create other user accounts, as a way to intelligently control administrator access to system resources.
The tools you use to create and maintain user accounts vary according to the type of account you are managing. Table 13.1 lists the various user accounts for the BIG-IP system and the tools you use to manage them.
The admin account
Configuration utility
(Users screen)
Configuration utility
(Users screen)
When you create configurable objects for the BIG-IP system, you have the option of putting those objects into administrative partitions. An administrative partition is a logical container of BIG-IP system objects such as virtual servers, pools, and monitors. When you first install the BIG-IP system, a default partition already exists named Common.
By putting objects into partitions, you establish a finer granularity of access control. Rather than having control over all resources on the BIG-IP system or no resources whatsoever, users with certain permissions can control resources within a designated partition only. For example, users with the role of Operator can mark nodes up or down, but can only mark those nodes that reside within their designated partition.
User accounts are another type of object that you can put into a partition. You put user accounts into administrative partitions strictly for the purpose of giving other users administrative access to those accounts. For example, you can put user accounts into partition B, and then assign a set of permissions (known as a user role) to user Jane so that she is allowed to modify user accounts in partition B.
Each user account on the BIG-IP system has a property known as Partition Access. The Partition Access property defines the partitions that the user can access. A user account can have access to either one partition or all partitions. Access to all partitions is known as universal access.
Figure 13.1, shows how partition access can differ for different user accounts on the BIG-IP system.
Figure 13.1 The Partition Access property for user accounts
In this example, the BIG-IP system objects reside in multiple partitions. Note that user accounts are also a type of BIG-IP system object, and as such, reside in a partition named Users. (Although you are not required to group user accounts together in a separate partition, for security purposes we highly recommend that you do so.)
To continue with the example, each user account in partition Users has access to specific, but different, partitions. Note that user accounts sjones, cjohnson, and gnelson can access one partition only, while the tbrown account has universal access.
To summarize, an administrative partition defines a set of objects, including user accounts, that other administrative users can potentially manage. This gives computing organizations greater control over user access to specific objects on the BIG-IP system.
To use the powerful user-roles feature, you should understand the available user roles and the ways that a user role affects a users access to objects residing within partitions.
User roles are a means of controlling user access to BIG-IP system resources. You assign a user role to each administrative user, and in so doing, you grant the user a set of permissions for accessing BIG-IP system resources.
The BIG-IP system offers several different user roles that you can choose from when assigning a role to an administrative user. Valid user roles are listed in Table 13.2.
A user role is a property of a user account. Each user role grants a different set of permissions. More specifically, a user role defines:
The resources that a user can manage
User roles define the types of resources, or objects, that a user can manage. For example, a user with the role of Operator can enable or disable nodes and pool members only. By contrast, a user with the Guest role cannot manage any BIG-IP system resources.
The tasks that a user can perform
For example, a user with the role of Operator can enable or disable nodes and pool members, but cannot create, modify, or delete them. Conversely, a user with the Manager role can perform all tasks related to partitioned objects (except for user accounts), including nodes and pool members.
Table 13.2, lists and describes the various user roles that you can assign to a user account.
Important: A role defines the type of objects that a user can manage and the tasks that a user can perform on those object types. A role does not define the set of specific, existing objects that the user can access. For information on defining user access to specific objects on the system, see Effect of user roles on objects within partitions.
This role grants users complete access to all partitioned and non-partitioned objects on the system. In addition, accounts with the Administrator role can change their own passwords.
Resource Administrator
This role grants users complete access to all partitioned and non-partitioned objects on the system, except user account objects. In addition, accounts with the Resource Administrator role can change their own passwords.
Users with the User Manager role that have access to all partitions can create, modify, delete, and view all user accounts except those that are assigned the Administrator role, or the User Manager role with different partition access. Accounts with the User Manager role that have access to all partitions can also change their own passwords.
Users with the User Manager role that have access only to a single partition can create, modify, delete, and view only those user accounts that are in that partition and that have access to that partition only. For example, if your user account has a User Manager role and has access to Partition A only, then you can manage only those user accounts that both reside in and have access to Partition A only.
User accounts with the User Manager role can change their own passwords.
This role grants users permission to create, modify, and delete virtual servers, pools, pool members, nodes, custom profiles, custom monitors, and iRules®. These users can view all objects on the system and change their own passwords.
This role grants users permission to create, modify, and delete iRules. Users with this role cannot affect the way that an iRule is deployed. For example, a user with this role can create an iRule but cannot assign it to a virtual server or move the iRule from one virtual server to another. A user with this role can be assigned universal access to administrative partitions.
This role grants users permission to modify nodes, pools, pool members, and monitors. These users can view all objects on the system and change their own passwords.
This role allows users to view, create, modify, and delete all WebAccelerator policy objects in all administrative partitions. Users can also view, create, update, and delete LTM Web Acceleration and HTTP Class profiles.
Web Application Security Administrator
This role grants users access to Application Security Manager security policy objects, in one or all administrative partitions. These users can modify HTTP Class profiles, but cannot create or delete them. More specifically, these users can access LTM objects in these ways:
These users have no access to other LTM objects, nor to any TMOS objects. They can, however, change change their own passwords. With respect to security policy objects, this role is similar to the Administrator role. You can assign this role only when the BIG-IP system includes the Application Security Manager component.
Web Application Security Editor
This role allows a user to configure or view most parts of the ASM module, in a specified administrative partition only. Specifically, these users have limited access to LTM objects, namely read-only permission for these profile types: HTTP, FTP, SMTP, and HTTP Class.
This role grants users permission to view all configuration data on the system, including logs and archives. Users with this role cannot create, modify, or delete any data, nor can they view SSL keys or user passwords.
This role grants users permission to view all objects on the system except for sensitive data such as logs and archives. Users with this role can change their own passwords.
The BIG-IP system automatically assigns a user role to an account when you create that account. The user role that the system assigns to a user account by default depends on the type of account:
root and admin accounts
The BIG-IP system automatically assigns the Administrator user role to the system maintenance root account and the admin account. You cannot change this user-role assignment. Thus, any user who successfully logs into the BIG-IP system using the root or admin account has full access to system resources and can perform all administrative tasks.
Other user accounts
The BIG-IP system automatically assigns the No Access user role to all standard user accounts other than the root and admin accounts. If the user account you are using has the Administrator role assigned to it, you are allowed to change another accounts user role from the default No Access role to any other user role, including Administrator. For remote user accounts, if you know that most of your administrative users need some amount of access to BIG-IP system resources, you can configure the BIG-IP system to use a role other than No Access as the default user role.
A user role defines the access level that a user has for each object in the users assigned partition. An access level refers to the type of task that a user can perform on an object. Possible access levels are:
Write
Grants full access, that is, the ability to create, modify, enable and disable, and delete an object.
Update
Grants the ability to modify, enable, and disable an object.
Enable/disable
Grants the ability to enable or disable an object.
Read
Grants the ability to view an object.
Managing local user accounts refers to the tasks of creating, viewing, modifying, and deleting user accounts that reside on the BIG-IP system, using the browser-based Configuration utility.
The Configuration utility stores local user accounts (including user names, passwords, and user roles) in a local user-account database. When a user logs into the BIG-IP system using one of these locally-stored accounts, the BIG-IP system checks the account to determine the user role assigned to that user account.
You assign a user role to an account at the time that you create the account, or by changing the properties of an existing account.
Important: Only users with the role of Administrator and User Manager can create and manage local user accounts. However, users with any role can change their own passwords. Also, if a user with a local user account is logged on to the BIG-IP system, and you subsequently switch the system from local authentication to remote authentication, the local user remains authenticated until the users logon session terminates.
A user account called admin resides on every BIG-IP system. Although the BIG-IP system creates this account automatically, you must still assign a password to the account before you can use it. To initially set the password for the admin account, you must run the Setup utility. To change its password later, you use the Configuration utilitys Users screens.
The admin account resides in the local user account database on the BIG-IP system. By default, the BIG-IP system assigns the Administrator user role, which gives the user of this account full access to all BIG-IP system resources. You cannot change the user role on this account. For detailed on user roles, see Understanding user roles.
The BIG-IP system includes an optional administrative feature: a security policy for creating passwords for local BIG-IP system user accounts. A secure password policy ensures that BIG-IP system users that have local user accounts create and maintain passwords that are as secure as possible.
Enforcement restrictions
These are, specifically, character restrictions that you can enable or disable. They consist of the minimum password length and the required character types (numeric, uppercase, lowercase, and other kinds of characters). When enabled, the BIG-IP system never enforces restrictions on user accounts that have the Administrator role assigned to them. Consequently, a user with Administrator permissions does not need to adhere to these restrictions when either changing his or her own password, or changing the passwords of other user accounts.
Policy restrictions
These restrictions represent the minimum and maximum lengths of time that passwords can be in effect. Also included in this type of policy restriction are the number of days prior to password expiration that users are warned, and the number of previous passwords that the BIG-IP system should store, to prevent users from re-using former passwords. When you have configured policy restrictions using the BIG-IP Configuration utility, policy restrictions apply to all user accounts, regardless of user role, except for user accounts with the Administrator role assigned to them. These restrictions are always enabled, although using the default values provides a minimal amount of restriction.
Note: The value of the Maximum Duration setting determines when users receive warning messages to change their passwords. If you change the value of this setting, any subsequent warning messages that users receive indicate the previous maximum duration value, rather than the new value. Once a user changes the password, however, subsequent reminder messages show the new value.
The password policy feature affects passwords for local user accounts only. Passwords for remotely-stored user accounts are not subject to this local password policy, but might be subject to a separate password policy defined on the remote system.
Important: You must have the user role of Administrator assigned to your account to configure this feature.
Table 13.3, shows the settings that you can configure, along with their descriptions and default values.
Secure Password Enforcement
Enables or disables character restrictions, that is, a policy for minimum password length and required characters. When you enable this setting, the Configuration utility displays the Minimum Length and Required Characters settings.
Specifies the minimum number of characters required for a password, and the allowed range of values is 6 to 255. This setting appears only when you enable the Secure Password Enforcement setting.
Important: When enabled, the BIG-IP system enforces this setting on user accounts with the Guest and Operator roles assigned to them; any user account with the Administrator role assigned to it (including the root and admin accounts) is not subject to the restrictions imposed by this setting.
Specifies the number of numeric, uppercase, lowercase, and other characters required for a password. The allowed range of values is 0 to 127. This setting appears only when you enable the Secure Password Enforcement setting.
Important: Any user account with the Administrator role assigned to it (including the root and admin accounts) is not subject to the restrictions imposed by this setting.
Specifies, for each user account, the number of former passwords that the BIG-IP system retains to prevent the user from re-using a recent password. The range of allowed values is 0 to 127. This setting applies to all user accounts.
Specifies the minimum number of days before a user can change a password. The range of allowed values is 0 to 255. This setting applies to all user accounts.
Specifies the maximum number of days that a user's password can be valid. The range of allowed values is 1 to 99999. This setting applies to all user accounts. For more information, see the note on the previous page.
Specifies the number of days prior to password expiration that the system sends a warning message to a user. The range of allowed values is 1 to 255. This setting applies to all user accounts.
Denies access to a user after the specified number of failed authentication attempts. The administrator can then reset the lock to re-enable access for the user.
Note: Whenever you change the secure password policy, the new configuration values, such as password expiration, do not apply to passwords that were created prior to the policy change. However, the new password policy takes effect the next time that the user changes his or her password.
You can deny access to a user after a configured number of failed authentication attempts. You can then reset the lock to re-enable access for the user.
To configure the maximum number of failures before user lockout, use the BIG-IP Configuration utility to locate the Users screen and then navigate to the Authentication screen. You can then specify a value for the Maximum Login Failures setting.
If a user becomes locked out, you can use the Unlock button on the User List screen to unlock the user.
A local user account stored on the BIG-IP system has several properties. Table 13.4 lists and describes these properties, along with their default values.
Specifies the name of the user account. The BIG-IP system is case-sensitive, which means that names such as JONES and Jones are treated as separate user accounts.
When viewing the properties of an existing user account, displays the name of the partition in which the user account resides. All partitionable BIG-IP system objects (including user account objects) have the Partition property. Note that you cannot edit the value of this setting.
Specifies the user role that you want to assign to the user account. For more information on these user roles, see Table 13.2.
Specifies the partition to which the user has access when logged on to the BIG-IP system. If you have permission to do so, you can assign this value to a new user account, or change this value on an existing user account.
This setting appears only when the user role for the account is not Administrator. (Accounts with the Administrator role always have universal partition access, that is, access to all partitions.)
Specifies the level of access to the BIG-IP system command line interface. Possible values are: Disabled and Advanced shell.
Users with the Administrator or Resource Administrator role assigned to their accounts can have advanced shell access, that is, permission to use all BIG-IP system command line utilities, as well as any Linux commands.
Depending on the user role assigned to your account (other than the No Access role), you can either create, view, modify, or delete local user accounts. Users with the Administrator user role assigned to their own accounts can perform all of these tasks with respect to user account objects.
When you create a local user account, you must give the account a name and a password. You must also set the user role, either by retaining the default user role or by assigning a new one. The default user role for local, non-system maintenance accounts is No Access.
Only users who have been granted the Administrator or User Manager role can create user accounts. If the user role assigned to your account is Administrator, you can create a user account in any partition on the system. If the user role assigned to your account is User Manager, you can create a user account in any partition to which you have access.
Note: User accounts on the BIG-IP system are case-sensitive. Thus, the system treats user accounts such as JONES and Jones as two separate user accounts. Note, however, that certain user names, such as admin, are reserved, and are therefore exempt from case-sensitivity. For example, you cannot create a user account named Admin, aDmin, or ADMIN.
Using the Configuration utility, you can easily display a list of existing local user accounts and view the properties of an individual account. Only users who have been granted the Administrator or User Manager roles can view the settings of other user accounts.
If the user role assigned to your account is Administrator, you can view any user account on the BIG-IP system, in any partition. If the user role assigned to your account is User Manager, you can view any user account in any partition to which you have access on the BIG-IP system.
To summarize, depending on their own partition access, users with a User Manager role can do some or all of the following:
Change the partition in which the user can access objects (applies only to users who have both a User Manager role and access to all partitions)
You use the Configuration utility to modify the properties of any existing local user account, other than the root account. When modifying user accounts, consider the following:
Only users who have been granted either the Administrator or User Manager role can modify user accounts other than their own account.
A user with the User Manager role can modify only those accounts that reside in the partition to which that user has access. For example, if user nelson has a User Manager role and has access to partition B only, he can modify only those user accounts that reside in partition B. Even in this case, however, for user accounts in partition B, user nelson cannot modify a users Partition Access property.

If, however, user nelson has a User Manager role and has access to all partitions, he can modify all user accounts on the system. This includes changing another users Partition Access property.
Users with any role but No Access can modify their own user accounts to change the password. These users cannot modify any other properties of their own user accounts.

Note: When a user changes their own password, the system automatically logs the user off of the Configuration utility. The system then requires the user to use the new password for subsequent logons. This behavior applies even when the new password matches the old password.
Users with the role of User Manager can modify all of the properties of their own user accounts, except their user role and partition access.
If you have an Administrator user role, you can also change some properties of the root account. Specifically, you can change the password of the root account, and you can enable or disable access to the BIG-IP system through SSH.
Warning: The Administrator user role provides access to the BIG-IP system prompt. If a user with the Administrator user role is currently logged on to the system and you change the user role to a role other than Administrator or Resource Administrator, the user can still run commands at the BIG-IP system prompt until he or she logs off of the system.
If the account you are using has the Administrator or User Manager user role, you can delete other local user accounts. A user with the Administrator role can delete any user account on the BIG-IP system in any partition. A user with the User Manager role can delete user accounts on the BIG-IP system in only those partitions to which she has access.
When you delete a local user account, you remove it permanently from the local user-account database on the BIG-IP system.
Note: You cannot delete the admin user account, nor can you delete the user account with which you are logged on.
Warning: The Administrator user role provides access to the BIG-IP system prompt. If a user with the Administrator user role is currently logged on to the system and you delete the user account, the user can still run commands at the BIG-IP system prompt until he or she logs off of the system.
Rather than store user accounts locally on the BIG-IP system, you can store them on a remote authentication server. In this case, you create all of your standard user accounts (including user names and passwords) on that remote server, using the mechanism supplied by that servers vendor.
Once you have created each user account on the remote server, you can then use the BIG-IP system to assign authorization properties (user role, partition access, and terminal access) for each account, for the purpose of controlling user access to BIG-IP system resources.
Important: You can assign authorization properties to remotely-stored user accounts on a group basis. You can then use the single configuration file (SCF) feature to propagate those properties to other BIG-IP devices on the network. For more information, see Assigning authorization for groups of user accounts, and the guide titled BIG-IP® Local Traffic Manager: Implementations.
The Configuration utility stores all local and remote access control information in the BIG-IP systems local user-account database. When a user whose account information is stored remotely logs into the BIG-IP system and is granted authentication, the BIG-IP system then checks its local database to determine the access control properties that you assigned to that user.
Note: The Configuration utility refers to remote user accounts as external users. An external user is any user account that is stored on a remote authentication server.
Important: Only users with the role of Administrator can manage user roles for remote user accounts. Also, if a user with a local user account is logged on to the BIG-IP system, and you subsequently switch the system from local authentication to remote authentication, the local user remains authenticated until the users logon session terminates.
One of the tasks you perform with the Configuration utility is to specify the type of remote user-account server that currently stores your remote user accounts. The available server types that you can specify are:
When you specify the type of remote server, you can also configure some server settings. For example, you can specify the user role you would like the BIG-IP system to assign to a remote account if you do not explicitly assign one.
Once you have configured the remote server, if you want any of the remote accounts to have a non-default user role, you can explicitly assign a user role to those accounts. For more information on user roles, see Understanding user roles.
If the remote authentication server is an Active Directory or LDAP server and is set up to authenticate SSL traffic, there is an additional feature that you can enable. You can configure the BIG-IP system to perform the server-side SSL handshake that the remote server would normally perform when authenticating client traffic. In this case, there are some preliminary steps you must perform to prepare for remote authentication using SSL.
You create BIG-IP system user accounts on your remote server using the mechanism provided by the vendor of your remote server. Then, as described in Specifying a remote user-account server, you use the Configuration utility to specify the remote authentication server that you are using to store those BIG-IP system user accounts. (Valid remote authentication servers for storing BIG-IP system user accounts are Active Directory, LDAP, RADIUS, and TACACS+.)
Once you have used the Configuration utility to specify the remote authentication server, you can configure authorization properties for the remote BIG-IP system user accounts. Specifically, you can do the following:
Assign unique authorization properties to an individual remote user account by creating a corresponding local user account, with the same user name, on the BIG-IP system and assigning access-control properties to it. For more information, see Assigning authorization to an individual user account.
Assign access-control properties on a group basis (that is, based on groups of users defined on a remote authentication server). For more information, see Assigning authorization for groups of user accounts.
The Authentication screen that you used to specify the type of remote authentication server also includes some default authorization values (for the Role, Partition Access, and Terminal Access settings). Therefore, if you do not explicitly configure these authorization settings for an individual BIG-IP system user account, the BIG-IP system assigns the default values to that account. This ensures that all remote user accounts have valid authorization settings assigned to them.
The default values for the Role, Partition Access, and Terminal Access settings are as follows:
Role--No Access
When you use these default values for a user account, the user account appears in the list of BIG-IP user accounts as Other External Users.
You can change the values that the BIG-IP system automatically uses as the default values for the Role, Partition Access, and Terminal Access settings.
To change the default authorization properties for remote user accounts, you configure the Role, Partition Access, and Terminal Access settings on the same Authentication screen that you used to specify the type of remote authentication server you are using.
Important: For the Other External Users user account, you can modify the Role, Partition Access, and Terminal Access settings only when your current partition on the BIG-IP system is set to Common. If you attempt to modify these settings when your current partition is other than Common, the system displays an error message.
Note that you can sometimes inadvertently affect your own user account, if the BIG-IP system is configured to perform remote user authentication, and you or another system administrator changes the default role or partition assigned to all external user accounts:
If you log on to the BIG-IP system using one of these remotely-authenticated Administrator accounts, and you or another Administrator user modifies the default role of all external accounts from Administrator to a lesser role, the system modifies the user role of your own account to the lesser role. However, the change to your own account does not actually occur until you log off and log on again to the BIG-IP system, thus allowing you to complete any tasks you initiated that still require the Administrator role.
Similarly, your user account can be affected if the BIG-IP system is configured to perform remote user authentication, and the default partition assigned to all external user accounts is a specific partition. In this case, if you are logged on to the BIG-IP system through the command line using one of the remotely-authenticated accounts, and another user who is logged on through the Configuration utility modifies the default partition for external users, the BIG-IP system immediately logs you off when you attempt to issue another command.
Important: If a BIG-IP system administrator changes the user role or partition assignment (or both) for any remote user account, the BIG-IP system logs off all users immediately. (A remote user account in this case refers to Other External Users.)
As stated in the previous section, you do not use the Configuration utility to create remote user accounts (user name and password) for the BIG-IP system. Instead, you create those user accounts on the remote server, using the mechanism provided by the remote server vendor. For authorization (access control) data, however, if you have the Administrator role assigned to your own user account, you can use the Configuration utility to explicitly assign access control properties to existing remote accounts.
Note: The BIG-IP system automatically assigns a default user role and other authorization properties to an existing remote account if you do not explicitly do so.
Remote user account names do not appear in the Configuration utility on the User List screen. Therefore, to assign non-default authorization properties to an existing remote account, you must simulate the creation of a new account on the BIG-IP system, configuring the User Name setting with the precise name of the existing remote account. You then configure the other properties on the Create screen as well. In this way, you assign authorization properties to an existing remote user account.
Use the following procedure to assign non-default authorization properties to an existing remote user account. (If you have already configured authorization properties of an individual account and want to change them again, see Changing authorization for an individual user account.)
Sometimes you might want to change the user role, partition access, and terminal access that you previously assigned to a remote account. To do so, you must change the properties of that account by clicking the account name on the User List screen. Only those remote user accounts to which you have explicitly assigned a user role appear in the list of user accounts.
Remote user accounts that simply inherit the default user role (configured when you specified the remote authentication server) appear in the list of remote user accounts under the name Other External Users. For more information about default authorization properties, see Understanding default remote-account authorization.
If you want to assign the same non-default access control properties to a group of remotely-stored user accounts, you can use the remote role groups feature. This feature stores all access control information on a group-wide basis for remotely-stored user accounts.
After using the remote role groups feature, you can propagate that access-control information to all BIG-IP devices on the network, using the single configuration file (SCF) feature. The remote role groups feature, combined with the SCF feature, removes the need to manually assign access control properties to each individual BIG-IP user within a group, on each BIG-IP device on your network.
When you initially configure a remote server for authentication of BIG-IP system users, all remote user accounts have access to the Common partition. If you want a specific remote account to have access to a partition other than Common, you can specify a different partition when you configure the authorization properties for that account. Remote accounts that have the Administrator user role assigned to them automatically have full access to all partitions on the BIG-IP system,
Using the Configuration utility, you can display a list of those remote user accounts to which you explicitly assigned a non-default user role. If a remote user account has the default role assigned to it, you cannot see that account in the list of remote user accounts.
When you use the Configuration utility to delete a remote user account, you are not actually deleting the account from the remote server. Instead, you are changing the values of the users authorization properties back to the default values. For more information on default authorization values, see Understanding default remote-account authorization.
The BIG-IP system generates a log message whenever a user or an application attempts to log on to or log off of the system. The system logs both successful and unsuccessful logon attempts. The system stores these log messages in the /var/log/secure file.
When the system logs an authentication message in the /var/log/secure file, the message can contain the following types of information:
Figure 13.2 shows examples of log messages for both successful and failed logon attempts made by user jsmith.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)