HP Fabric OS 7.1.0, Руководство администратора

Страница: 174 / 666

174 Fabric OS Administrator’s Guide
53-1002745-02
Remote authentication
5
Configuring the password expiration date
FabricOS lets you configure a password expiration date for each user account and to configure a
warning period for notifying the user that the account password is about to expire. To configure
these values, set the following attributes:
•
brcd-passwd-expiryDate sets the password expiration date in mm / dd / yyyy format.
•
brcd-passwd-warnPeriod sets the warning period as a number of days.
The following example sets the password expiration date for the fosuser5 account. It also specifies
that a warning be sent to the user 30 days before the password is due to expire.
user = fosuser5 {
pap = clear "password"
chap = clear "password"
password = clear "password"
service = shell {
set brcd-role = securityAdmin
set brcd-passwd-expiryDate = 03/21/2014;
set brcd-passwd-warnPeriod = 30;
}
}
Configuring a Windows server
FabricOS is compatible with any freeware for Microsoft Windows that uses
protocol version v1.78. Refer to the vendor documentation for configuration details.
Remote authentication configuration on the switch
At least one RADIUS, LDAP, or server must be configured before you can enable a remote
authentication service. You can configure the remote authentication service even if it is disabled on
the switch. You can configure up to five RADIUS, LDAP, or servers. You must be logged in
as admin or switchAdmin to configure the RADIUS service.
NOTE
On dual-CP Backbones (Brocade DCX, DCX-4S, DCX 8510-4, and DCX 8510-8 devices), the switch
sends its RADIUS, LDAP, or request using the IP address of the active CP. When adding
clients, add both the active and standby CP IP addresses so that users can still log in to the switch
in the event of a failover.
RADIUS, LDAP, or configuration is chassis-based configuration data. On platforms
containing multiple switch instances, the configuration applies to all instances. The configuration is
persistent across reboots and firmware downloads. On a chassis-based system, the command
must replicate the configuration to the standby CP.
Multiple login sessions can invoke the aaaConfig command simultaneously. The last session that
applies the change is the one whose configuration is in effect. This configuration is persistent after
an HA failover.
The authentication servers are contacted in the order they are listed, starting from the top of the
list and moving to the bottom.