CONFIGURING


Active Directory password synchronization

WARNING: This feature impacts your Active Directory domain controller configuration; proceed only with a working backup of your domain controller. See further details in this topic.

This feature applies the Windows passwords of users registered in an Active Directory domain to their Domino HTTP and/or Notes ID passwords. Note that industry best practice encourages the use of federated login using a single password authority and discourages syncing of passwords across multiple systems.

When a user whose Active Directory information is synced to Domino changes their Windows domain password, a Domino password filter that is installed and runs on an Active Directory domain controller creates a password change request. The Domino password filter pushes the request to a Domino server in the domain that is designated as a Request Processor. The Request Processor processes the password change request by applying the new password to the user's HTTP password, to the Notes ID password in the ID vault, or to both passwords.

This feature is primarily useful for environments that do not use federated SAML authentication that want to unlock Notes IDs and apply the Active Directory passwords to them. For example, HCL Nomad mobile users can benefit from this as can disconnected, offline users who can't connect to an Active Directory domain controller.

This feature requires the ability to extract passwords from Active Directory to re-apply the passwords to the Notes IDs in the vault. Microsoft provides an API call exactly for this purpose. This API can be used only from software installed on the Active Directory domain controller, which is why Domino is installed there for this feature.

Note: The implementation used by Domino to obtain the Active Directory password is the only secure method available. The LDAP protocol can not be used.

Password synchronization is supported for:


Requirements
Note:
Precautions

Active Directory password synchronization runs in the Local Security Authority Subsystem (lsass.exe) in the Windows kernel. HCL has tested Active Directory password synchronization on clean operating system installs with no third party software installed. HCL can't test with other third-party software that may interact with the LSASS, such as anti-virus and anti-malware programs. Therefore HCL strongly recommends taking the following precautions when testing and deploying Active Directory password synchronization in your environment:


Note: The Active Directory password synchronization password filter is not digitally signed by Microsoft and does not run on domain controllers that are running with LSA protection enabled.