HP UX Red Hat Direry Server Software manual Replicating Account Lockout Attributes

Replicating Account Lockout Attributes

print "replace:nsds5ReplicaUpdateSchedule";}

/^nsds5ReplicaUpdateSchedule: / { s = 1; print $0; }/^$/{if ( $s == 1 ){ print "-" ;

print ""; }else{ print "nsds5ReplicaUpdateSchedule: 0000-2359 0123456";print "-" ;

print ""; };s = 0; }

' > /tmp/ldif.$$echo "Ldif is in /tmp/ldif.$$"echo

ldapmodify -c -h ${SUP_HOST} -p ${SUP_PORT} -D "${SUP_MGRDN}" \-w ${SUP_MGRPW}

-f /tmp/ldif.$$

Example 8.1. Replicate_Now Script Example

Variable	Definition
supplier_hostname	Hostname of the supplier to contact for
	information on replication agreements with the
	current consumer.
supplier_portnumber	LDAP port in use on the supplier.
supplier_directoryManager	DN of the privileged Directory Manager user
	on the supplier.
supplier_directoryManager_password	Password of the privileged Directory Manager
	user on the supplier.
consumer_hostname	Hostname of the current consumer.
consumer_portnumber	LDAP port in use on the consumer.

Table 8.4. Replicate_Now Variables

For the update operation to occur over an SSL connection, modify the ldapmodify command in the script with the appropriate parameters and values. For more information on the ldapmodify command, see Section 2, “Managing Entries from the Command-Line”and the Directory Server Configuration, Command, and File Reference.

12. Replicating Account Lockout Attributes

Account lockout policies will block a user ID from being able to access the Directory Server if the login attempt fails a set number of times. This prevents hackers or other malicious people from illegitimately accessing the Directory Server by guessing a password. Password policies are set locally, and generally account lockout attributes are local to each replica. This means that a person can attempt to log in to one replica until the account lockout count is reached, then try again immediately on another replica. The way to prevent that is to replicate the

331