The following sections explain the retry methods used after a synchronization failure:
If a password change sent from Active Directory is not successfully completed in the Identity Vault, the driver caches the password. It is not retried again until an Add or Modify event occurs for the user that the password belongs to. (Previously, these saved passwords were retried at every polling interval.)
When the driver polls for changes in Active Directory, the driver receives Add or Modify events for users. For each user Add or Modify event, the driver checks to see if it has a password saved for this new user. If it does, the driver sends the password to the Identity Vault as a Modify user event.
If you have set up password synchronization to send e-mail messages to users when password synchronization fails, this enhancement minimizes the number of e-mails that a user might receive.
The Password Expiration Time parameter lets you determine how long to save a particular user’s password if synchronization is not successful on the first try. The driver saves a password until it is successfully changed in the Identity Vault, or until the Password Expiration Time elapses.
You are prompted to specify an expiration time when you import the sample driver configuration. If you don’t specify a time, or if the interval field contains invalid characters, the default setting is 60 minutes. If the time specified is less than three times the polling interval specified, the driver changes the time to be three times the polling interval.
Set the value large enough to handle whatever temporary backlog of passwords exists. If you are doing bulk changes, set the timeout large enough to handle all the changes. The rule of thumb is to allow one second per password. For example, to synchronize 18,000 passwords, allow 300 minutes (18,000 passwords divided by 60 seconds).
A setting of -1 is indefinite. Although this setting can handle bulk changes, it can cause problems. For example, a password might never be synchronized because the account wasn’t associated. Such a password would remain in the system forever. A number of similar situations could result in a large inventory of unsynchronized passwords held by the system.
On the Publisher channel, password synchronization might occur before the Add event. The driver retries immediately following the Add event.
A new user with a password is created in Active Directory. The filter immediately sends the new password to the driver. However, the driver hasn’t yet received that user Add event because the event occurred between polling intervals. Because the driver has not yet created the user in the Identity Vault, the password synchronization is not successful on this first attempt. The driver caches the password.
At the next polling interval, the driver receives the Add user event for the new user. The driver also checks to see if it has a password cached for this new user. The driver sends the Add user event to the Identity Vault, and also sends a Modify user event to synchronize the password.
In this case, the password synchronization is delayed by only one polling interval.
The Password Expiration Time parameter doesn’t have an effect in this situation.
A new user with a password is created in Active Directory. However, the user information doesn’t meet the requirements of the Create policy for the Active Directory driver.
For example, perhaps the Create rule requires a full name, and the required information is missing. Like the No Effect example, the filter immediately sends the password change to the driver. However, on the first try the password change is not successful in the Identity Vault because the user doesn’t exist yet. The driver caches the password.
In this case, however, even when the driver polls for changes in Active Directory and discovers the new user, the driver can’t create the new user because the user information doesn’t meet the Create policy’s requirements.
Creating the new user and synchronizing the password are delayed until all the user information is added in Active Directory to satisfy the Create policy. Then the driver adds the new user in the Identity Vault, checks to see if it has a password cached for this new user, and sends a Modify user event to synchronize the password.
The Password Expiration Time parameter affects this scenario only if the time interval elapses before the user information in Active Directory meets the requirements of the Create policy. If the Add event comes in after the password has expired and the driver doesn’t have the password cached for that user, synchronization can’t occur. Because the driver doesn’t have a cached password, the driver uses the default password in the password policy.
After the user changes the password in either Active Directory or the Identity Vault, that password is synchronized.
If Password Synchronization is set up for bidirectional flow of passwords, a password can also be synchronized from the Identity Vault to Active Directory when a password change is made in the Identity Vault.
If your Create policy is restrictive, and it generally takes longer than a day for a new user’s information to be completed in Active Directory, you might want to increase the Password Expiration Time parameter interval accordingly. The driver can then cache the passwords until the user is finally created in the Identity Vault.
A user with a password is created in Active Directory. However, this user never meets the criteria of the Create policy for the Active Directory driver.
For example, perhaps the new user in Active Directory has a Description that indicates the user is a contractor, and the Create policy blocks creation of User objects for contractors because the business policy is that contract employees are not intended to have a corresponding user account in the Identity Vault. Like the previous example, the filter immediately sends the password change, but the password synchronization isn’t successful on the first attempt. The driver caches the password.
In this case, a corresponding user account is never created in the Identity Vault. Therefore, the driver never synchronizes the cached password. After the Password Expiration Time has passed, the driver removes the user password from its cache.
Markus has an Active Directory account and a corresponding Identity Vault account. He changes his Active Directory password, which contains six characters. However, the password doesn’t meet the eight-character minimum required by the Password policy that the administrator created in eDirectory. Password Synchronization is configured to reject passwords that do not meet the policy and to send a notification e-mail to Markus saying that password synchronization failed. The driver caches the password and retries it only if a change is made to the User object in Active Directory.
In this case, shortly after changing a password, Markus receives an e-mail stating that the password synchronization wasn’t successful. Markus receives the same e-mail message each time the driver retries the password.
If Markus changes the password in Active Directory to one that complies with the Password policy, the driver synchronizes the new password to the Identity Vault successfully.
If Markus doesn’t change to a compliant password, the password synchronization is never successful. When the Password Expiration Time elapses, the driver deletes the cached password and no longer retries it.