- Edit the security.conf file.
-
Set the account.lock.num parameter.
Note: When you use Ops Center Automator in a cluster environment, you must edit the security.conf file on both the active and standby nodes.
Specify the number of consecutive failed login attempts required to trigger automatic account locking. Specify a value from 0 to 10. If a user makes the specified number of unsuccessful login attempts, the account will be locked. If you specify 0, any number of unsuccessful login attempts is allowed.
Default: 0
CAUTION:-
If you change the number of consecutive failed login attempts, the new value takes effect from the first failed login after the change. If a user is currently logged in and you attempt to login using his or her account, but you fail the specified number of times, his or her user account will be locked. However, the user can continue to perform operations while still logged in.
-
You can also set an account locking policy from the GUI. However, if the system is in a cluster configuration, the settings from the GUI are applied only to the executing node. To apply the settings to the standby node, switch the nodes, and then specify the same settings.
-
You can set an account locking policy for
Common Component products in the security.conf file.
If you change the setting values in
the security.conf file, the new account locking policy takes effect
immediately.