Applies To:

Show Versions Show Versions

Manual Chapter: Managing User Accounts
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

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. For information on creating and managing local user accounts, see Managing local user accounts.
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:
There are two types of user accounts on the BIG-IP system: System maintenance accounts and standard user accounts.
System maintenance accounts
System maintenance accounts are user accounts that you maintain using the Setup utility. There are two types of system maintenance accounts: the root account and the support account. System maintenance accounts reside locally on the BIG-IP system and grant full access to BIG-IP system resources. You configure and maintain these accounts 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. 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 accounts other than the system maintenance accounts (root and support) and the admin user account, but we recommend that you do so, 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 4.1 lists the various user accounts for the BIG-IP system and the tools you use to manage them.
The root account
Configuration utility (Platform screen)
The support account
Configuration utility (Platform screen)
The admin account
Configuration utility
(Users screen)
Configuration utility
(Users screen)
When you create a user account, you assign a user role to that account. Alternatively, you can use the default user role for an account. To implement the user-roles feature, you should understand the differences in the available user roles.
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 different user roles that you can choose from when assigning a role to an administrative user. Valid user roles are:
No Access
A user with the No Access user role has no access to the BIG-IP system. This is the default user role for any user account other than the admin account.
Guest
The Guest user role grants read-only access to the BIG-IP system. A user with this role can view configuration information, but cannot create, modify, or delete BIG-IP system objects. Users with this access level therefore do not have access to various Configuration utility elements such as Create buttons, Update buttons, and Delete buttons.
Operator
The Operator user role allows the user to view information and to enable or disable nodes. Users with this access level therefore do not have access to various Configuration utility elements such as Create buttons, Update buttons, and Delete buttons.
Administrator
The Administrator user role provides the user with full access to all administrative tasks. By default, users with this user role can access the BIG-IP system through the Configuration utility and iControl, but not through the command line interface. However, as an option, you can assign users the ability to also access the BIG-IP system through the command-line interface.
A user role is a property of a user account. Each user role grants a different set of permissions and access. Table 4.2 lists the various user roles, and shows the permissions and type of system access that each user role grants to a user.
(enable and disable only)
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 admin account. 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.
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 can create and manage local user accounts. However, users with the Guest or Operator role can change their own passwords.
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.
Important: You must have the user role of Administrator assigned to your account to configure this feature.
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 enforces restrictions on user accounts with the Guest or Operator user role, and 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.
Password policy restrictions
These restrictions represent the minimum and maximum lengths of time that passwords can be in effect. Also included in these password policy restrictions 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. Password policy restrictions apply to all user accounts, regardless of user role assigned to them. These restrictions are always enabled, although using the default values provides a minimal amount of restriction.
The value of the Maximum Duration setting determines when users will 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.
Table 4.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 or Operator role assigned to them; any user account with the Administrator role assigned to it (including the root, support, 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: When enabled, the BIG-IP system enforces this setting on user accounts with the Guest or Operator role assigned to them. Any user account with the Administrator role assigned to it (including the root, support, 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 6 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.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The Users screen opens.
2.
On the menu bar, click Authentication.
This displays the screen for implementing a password policy.
3.
Under Password Policy, locate the Secure Password Enforcement setting and set it to meet your needs:
If you want to enable character restrictions for Guest and Operator accounts, locate the Secure Password Enforcement setting and select Enabled.
This displays the Minimum Length and Restrictions settings on the screen. Retain or change the values for these settings.
If you do not want to enable character restrictions for Guest and Operator accounts, leave the Secure Password Enforcement setting set to Disabled.
4.
Retain the default values for all other settings, or change them to suit your needs.
These settings represent the secure password policy restrictions, which apply to all user accounts, regardless of user role.
5.
Click Finished.
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 policy takes effect the next time that the user changes his or her password.
A local user account stored on the BIG-IP system has several properties. Table 4.4 lists and describes these properties, along with their default values.
Specifies the user role that you want to assign to the user account. Allowed values are: Administrator, Operator, Guest, and No Access. For more information on these user roles, see Table 4.2.
Allows or prevents access to the BIG-IP system command line interface. When you enable this setting:
Users with the Administrator role assigned to their accounts have permission to use all BIG-IP system command line utilities, as well as any operating system commands that do not require root privilege.
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 accounts is No Access.
Only users who have been granted the Administrator role can create user accounts.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens, displaying a list of all local accounts.
2.
In the upper right corner of the screen, click Create.
The New User screen opens.
3.
In the User Name box, type a name for the user account.
4.
For the Password setting, type and confirm a password for the account.
For more information on user account passwords, see Managing remote user accounts.
5.
To grant an access level other than No Access, use the Role setting and select a user role.
6.
7.
Click Finished.
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 role 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.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens, displaying a list of all standard user accounts.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens, displaying a list of all standard user accounts.
2.
In the user-account list, find the user account you want to view and click the account name.
This displays the properties of that user account.
You use the Configuration utility to modify the properties of any existing local user account, other than the root account. Only users who have been granted the Administrator role can modify user accounts other than their own.
Users with the Guest or Operator role can modify their own user accounts to change the password. These users cannot modify any other properties of their own user accounts.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens, displaying a list of all standard user accounts.
2.
In the user account list, click a user account name.
This displays the properties of that account.
The Password setting
The Role setting
The Terminal Access setting
4.
Click Update.
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.
1.
On the Main tab of the navigation pane, expand System, and click Platform.
The General screen opens.
2.
For the Root Account setting, type a new password in the Password box, and re-type the new password in the Confirm box.
3.
If you want to grant SSH access, then for the SSH Access setting, check the Enabled box, and for the SSH IP Allow setting, either:
Select * All Addresses.
Select Specify Range and type a range of IP addresses.
4.
Click Update.
Important: If you have a redundant system configuration and you change the password on the admin account, you must also change the password on the peer unit, to ensure that synchronization of configuration data operates correctly.
If the account you are using has an Administrator 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, except for the root, support, and admin accounts.
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 in.
1.
On the Main tab of the navigation pane, expand System, and click Users.
This opens the User List screen, displaying a list of all standard user accounts.
2.
In the user account list, locate the name of the account you want to delete and click the Select box to the left of the account name.
3.
Click the Delete button.
A confirmation box appears.
4.
Click Delete again.
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.
Authentication for remote user accounts is based on standard HTTP authentication, that is, user name and password. The exception to this is when the remote server is specifically configured to perform SSL authentication. In this case, authentication is based on SSL certificates.
Once you have created each user account on the remote server, you can then use the BIG-IP system to assign a user role to that account, for the purpose of controlling user access to BIG-IP system resources.
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.
You assign a user role to a remote account using the Configuration utility. First, you specify the type of remote authentication server (database) that stores the remote user accounts. Then, you configure each user account to assign a user role to that account. For those remote accounts to which you do not assign a user role, the BIG-IP assigns a default user role that you define when you identify the remote server type.
The Configuration utility stores all local and remote user-role 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 user role that you assigned to that user.
Important: Only users with the role of Administrator can manage user roles for remote user accounts.
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.
2.
On the BIG-IP system, import the certificates, using the Configuration utility.
You can store the certificates in any location on the BIG-IP system. For information on importing certificates, see the Configuration Guide for BIG-IP® Local Traffic Management.
Note: Configuring remote authentication using the following procedures creates a user account on the BIG-IP system named Other External Users. For more information on this account, see Understanding default remote-account authorization.
To configure remote Active Directory or LDAP authentication for BIG-IP system administrative users
1.
On the Main tab of the navigation pane, expand System, and click Users.
The Users screen opens.
2.
On the menu bar, click Authentication.
The Authentication screen opens.
3.
Click Change.
4.
From the User Directory list, select Remote - Active Directory or Remote - LDAP.
5.
In the Host box, type the IP address of the remote server.
6.
For the Port setting, retain the default port number (389) or type a new port number in the box.
This setting represents the port number that the BIG-IP system uses to access the remote server.
7.
In the Remote Directory Tree box, type the file location (tree) of the user authentication database on the Active Directory or LDAP server. At minimum, you must specify a domain component (that is, dc=<value>).
8.
For the Scope setting, retain the default value (Sub) or select a new value.
This setting specifies the level of the remote server database that the BIG-IP system should search for user authentication. For more information on this setting, see the online help.
9.
For the Bind setting, specify a user ID login for the remote server:
a)
In the DN box, type the Distinguished Name for the remote user ID.
b)
In the Password box, type the password for the remote user ID.
c)
In the Confirm box, re-type the password that you typed in the Password box.
10.
In the User Template box, type the distinguished name of the user logging in to the system.
You specify the template as a variable that the system replaces with user-specific information during the login attempt. For example, you can specify a user template such as %s@siterequest.com or uid=%s,ou=people,dc=siterequest,dc=com.
11.
If you want to enable SSL-based authentication, click the SSL box and if necessary, configure the following settings.
Important: Be sure to specify the full path name of the storage location on the BIG-IP system. For example, if the certificate is stored in the directory /config/bigconfig/ssl.crt, type the value /config/bigconfig/ssl.crt.
a)
In the SSL CA Certificate box, type the name of a chain certificate, that is, the third-party CA or self-signed certificate that normally resides on the remote authentication server.
b)
In the SSL Client Key box, type the name of the client SSL key.
Use this setting only in the case where the remote server requires that the client present a certificate. If a client certificate is not required, you do not need to configure this setting.
c)
In the SSL Client Certificate box, type the name of the client SSL certificate.
Use this setting only in the case where the remote server requires that the client present a certificate. If a client certificate is not required, you do not need to configure this setting.
12.
From the Role list, select a user role that you want the BIG-IP system to assign as the default role for remote user accounts.
The BIG-IP system assigns this user role to any remote user account to which you do not explicitly assign a role. For more information, see Understanding default remote-account authorization.
13.
If you want to enable terminal access for the remote user accounts, use the Terminal Access list to select Enabled.
If you select Enabled, the BIG-IP system grants terminal access to remote user accounts by default.
14.
Click Finished.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The Users screen opens.
2.
On the menu bar, click Authentication.
The Authentication screen opens.
3.
Click Change.
4.
From the User Directory list, select Remote - RADIUS.
5.
From the Server Configuration box:
If you want to use a secondary RADIUS server in the event that the primary server becomes unavailable, select Primary & Secondary.
This causes the Secondary setting to appear.
6.
For the Primary setting, configure these settings for the primary RADIUS server:
a)
In the Host box, type the IP address of the remote server.
b)
In the Port box, retain the default port number (1812) or type a new port number in the box.
This setting represents the port number that the BIG-IP system uses to access the remote server.
c)
In the Secret box, type the RADIUS secret.
d)
In the Confirm box, re-type the secret that you typed in the Secret box.
Note that the values of the Secret and Confirm settings must match.
7.
If you selected Primary & Secondary from the Server Configuration box, configure the Host, Port, Secret, and Confirm settings for the secondary server, using the instructions in the previous step.
8.
From the Role box, select a user role that you want the BIG-IP system to assign as the default role for remote user accounts.
The BIG-IP system assigns this user role to any remote user account to which you do not explicitly assign a role. Once you have used this screen to set up the RADIUS server, the BIG-IP system assigns this user role to any remote user account to which you do not explicitly assign a role. For more information, see Understanding default remote-account authorization.
9.
If you want to enable terminal access for the remote RADIUS user accounts, use the Terminal Access box to select Enabled.
If you select Enabled, the BIG-IP system grants terminal access to remote user accounts by default.
10.
Click Finished.
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 then use the Configuration utility to specify the remote authentication server that stores BIG-IP system user accounts.
Part of specifying the remote authentication server is configuring certain authorization properties for remote accounts. Specifically, you specify a default user role and terminal access for all user accounts to which you have not individually assigned authorization properties. For more information, see Understanding default remote-account authorization.
Once you have specified the remote server, including the default authorization properties, you can do the following:
Sometimes, you might have remote user accounts to which you have not explicitly assigned a user role and terminal access. Such accounts appear in the list of user accounts on the User List screen as Other External Users.
To ensure that these accounts have a user role and terminal access assigned to them, the BIG-IP system automatically assigns default values for these properties, to ensure valid user authorization. By default, the authorization values that the BIG-IP system assigns to remote accounts are the authorization properties that you configured as part of specifying the remote authentication server. Table 4.5 lists these properties and their default values.
You can change the values that the BIG-IP system uses as the default Role and Terminal Access values. (See To change the default remote-account authorization, following.) Then, whenever you create a user account on the remote server and you do not explicitly assign a user role and terminal access to that account, the BIG-IP system automatically assigns the specified default values to the account.
To change the default remote-account authorization properties, you configure the Role and Terminal Access settings on the Authentication screen that you use to specify the type of remote authentication server you are using.
1.
On the Main tab of the navigation pane, expand System, and click Users.
This opens the User List screen, displaying a list of all standard user accounts.
2.
On the menu bar, click Authentication.
This displays the Authentication screen.
3.
Click Change.
4.
From the User Directory list, select Remote - Active Directory, Remote - LDAP, or Remote - RADIUS.
5.
From the Role list, select a default user role.
The BIG-IP system assigns this user role to any remote account to which you have not explicitly assigned a user role.
6.
From the Terminal Access list, select Enabled or Disabled.
7.
Click Update.
As stated in the previous section, you do not use the Configuration utility to create remote user accounts for the BIG-IP system. However, if you have the Administrator role assigned to your own user account, you can use the Configuration utility to explicitly assign authorization properties (such as a user role) to existing remote accounts.
Note that the BIG-IP system automatically assigns a default user role to a remote account if you do not explicitly do so. For information on configuring the default user role, see To change the default remote-account authorization.
Use the following procedure to configure the authorization properties of an existing remote user account, if you have not already done so. (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.)
In this procedure, instead of selecting the account name from a list of user accounts and then modifying its properties, you simulate the creation of a new account, configuring the User Name property with the precise name of the existing account. You then configure the other properties on the Create screen as well. In this way, you actually modify the properties of the existing remote account.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens.
Note: You do not see the user account in the list of user accounts.
2.
In the upper-right corner of the screen, click Create.
This displays the New User screen.
3.
In the User Name box, type the name of the remote user to which you want to assign a user role.
Important: This user name must precisely match the user name assigned to the remote user account.
4.
For the Role setting, select a user role.
5.
From the Terminal Access box, select Enabled or Disabled, to allow or prevent access to the BIG-IP system through the command line interface.
6.
Click Finished.
Sometimes you might want to change the user role 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. For the procedure on changing the authorization properties for this type of account, see To change authorization for an individual user account, following.
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. Consequently, you cannot change the authorization properties for any individual account of this type, that is, any account that has inherited the default authorization properties. For more information on assigning default authorization properties, see Understanding default remote-account authorization.
1.
On the Main tab of the navigation pane, expand System, and click Users.
This opens the User List screen, displaying a list of user accounts to which you explicitly assigned user roles.
2.
In the User Name column, click a user name.
This displays the properties for that user account.
3.
From the Role list, select a user role.
4.
From the Terminal Access list, select Enabled or Disabled.
5.
Click Update.
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.
1.
On the Main tab of the navigation pane, expand System, and click Users.
The User List screen opens, displaying a list of all standard user accounts.
2.
On the menu bar, click Authentication.
The Authentication screen opens.
3.
Verify that the User Directory setting specifies a remote authentication server type (Active Directory, LDAP, or RADIUS).
5.
View the list of user accounts.
Remote user accounts that are assigned the default user role appear in the list as Other External Users.
2.
In the user-account list, find the user account you want to view and click the account name.
This displays the properties of that user account.
Note: The only properties displayed for a remote user account are the account name, the user role assigned to the account, and the accounts terminal access.
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.
1.
On the Main tab of the navigation pane, expand System, and click Users.
This opens the User List screen, displaying a list of all standard user accounts.
3.
Click Delete.
A confirmation page appears.
4.
Click Delete.
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)