| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Identity Synchronization for Windows 6.0 Deployment Planning Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Identity Synchronization for Windows 6.0 Deployment Planning Guide |
2. Case Study: Deploying in a Multimaster Replication Environment
3. Case Study: Deploying in a High-Availability Environment Over a Wide Area Network Using SSL
A. Pluggable Authentication Modules
B. Identity Manager and Identity Synchronization for Windows Cohabitation
Identity Manager and Identity Synchronization for Windows Functionality
Password Changes on Directory Server
Password Changes and Provisions Originating from Identity Manager Console
Configuring Identity Manager and Identity Synchronization for Windows
Setting Up Identity Manager 5.0 SP2 and Later
Configuring pwsync to Not Propagate Passwords to Directory Server
Setting Up Identity Manager 5.0 SP1 and Earlier
Configuring Identity Synchronization for Windows
Passwords modified on Active Directory are propagated through the Identity Manager-Identity Synchronization for Windows deployment as described below (See Overview for illustration):
The user resets the password on Active Directory by using the Change Password option in the Task Manager dialog of Windows.
Identity Synchronization for Windows detects the change and sets a password invalid flag on the corresponding user entry in the Identity Synchronization for Windows-managed Directory Server.
The user connects to Directory Server for the password change to be complete (see On Demand Synchronization in the Sun Java System Directory Server Enterprise Edition 11.1.1 Installation Guide.)
Identity Manager’s pwsync command also detects the password change and propagates it to all other Identity Manager-managed resources, except Directory Servers.
|