What steps will reproduce the problem?
1. Enable multiple LDAP servers inside the PWM config Manager
2. Go to the frontend and reset a password for a user
What is the expected output? What do you see instead?
I would expect that PWM ensures that all replicas are in sync by
callingChaiUtility.testAttributeReplication. This is done, however only the
current connected LDAP server is checked. Other LDAP servers from the
ChaiConfiguration are not tested.
Relevant part of catalina.out (anonymized)
2013-08-21 10:34:56, DEBUG, operations.UserStatusHelper, {2,testuser} wrote
pwdLastModified update attribute for cn=123456789,ou=users,o=meta
[123.456.789.12]
2013-08-21 10:34:56, TRACE, operations.PasswordUtility, {2,testuser} beginning
password replication checking [123.456.789.12]
2013-08-21 10:34:57, TRACE, util.ChaiUtility, testAttributeReplication, will
test the following ldap urls: [ldaps://ldap1.example.com:636]
2013-08-21 10:34:57, TRACE, provider.JNDIProviderImpl, bind successful as
cn=pwm_proxy,o=meta (78ms)
2013-08-21 10:34:57, TRACE, provider.ChaiProviderFactory, adding
WatchdogWrapper to provider instance
2013-08-21 10:34:57, TRACE, provider.WatchdogWrapper, checking for user
password expiration to adjust watchdog timeout
2013-08-21 10:34:57, TRACE, provider.ChaiProviderFactory, adding
StatisticsWrapper to provider instance
2013-08-21 10:34:57, DEBUG, util.ChaiUtility, testAttributeReplication for
EntryDN: cn=123456789,ou=users,o=meta:TestAuxLastPwdUpdate 1 up, 0 down, 1 in
sync
I'm not sure whether this is a PWM bug or an LDAP Chai bug.
Original issue reported on code.google.com by sebastia...@gmail.com on 21 Aug 2013 at 2:56
Original issue reported on code.google.com by
sebastia...@gmail.comon 21 Aug 2013 at 2:56