search

zzOzz / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

Password change taking 2minutes in PWM #561

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
When I try to change password for user after login, It is taking 2 minutes.
Login process does not have issue in PWM.

What is the expected output? What do you see instead?

What version of PWM are you using?

v1.7.0
What ldap directory and version are you using?
openldap 2.4

Please paste any error log messages below:
 no error message but below  trace is repeating when password change is taking too long. Let me know if you need trace of the log.

2014-04-23 17:30:35, TRACE, provider.ChaiProviderFactory, adding 
WatchdogWrapper to provider instance
2014-04-23 17:30:35, TRACE, provider.WatchdogWrapper, checking for user 
password expiration to adjust watchdog timeout
2014-04-23 17:30:35, TRACE, provider.ChaiProviderFactory, adding 
StatisticsWrapper to provider instance
2014-04-23 17:30:35, DEBUG, util.ChaiUtility, testAttributeReplication for 
EntryDN: cn=pwmadmin,dc=pccwglobal,dc=net:pwmLastPwdUpdate 0 up, 1 down, 0 in 
sync
2014-04-23 17:30:37, TRACE, util.ChaiUtility, testAttributeReplication, will 
test the following ldap urls: [ldap://63.220.240.90:389]
2014-04-23 17:30:37, TRACE, provider.JNDIProviderImpl, bind successful as 
cn=admin,dc=pccwglobal,dc=net (0ms)
2014-04-23 17:30:37, TRACE, provider.ChaiProviderFactory, adding 
WatchdogWrapper to provider instance
2014-04-23 17:30:37, TRACE, provider.WatchdogWrapper, checking for user 
password expiration to adjust watchdog timeout
2014-04-23 17:30:37, TRACE, provider.ChaiProviderFactory, adding 
StatisticsWrapper to provider instance
2014-04-23 17:30:37, DEBUG, util.ChaiUtility, testAttributeReplication for 
EntryDN: cn=pwmadmin,dc=pccwglobal,dc=net:pwmLastPwdUpdate 0 up, 1 down, 0 in 
sync
2014-04-23 17:30:39, TRACE, util.ChaiUtility, testAttributeReplication, will 
test the following ldap urls: [ldap://63.220.240.90:389]
2014-04-23 17:30:39, TRACE, provider.JNDIProviderImpl, bind successful as 
cn=admin,dc=pccwglobal,dc=net (0ms)
2014-04-23 17:30:39, TRACE, provider.ChaiProviderFactory, adding 
WatchdogWrapper to provider instance
2014-04-23 17:30:39, TRACE, provider.WatchdogWrapper, checking for user 
password expiration to adjust watchdog timeout
2014-04-23 17:30:39, TRACE, provider.ChaiProviderFactory, adding 
StatisticsWrapper to provider instance
2014-04-23 17:30:39, DEBUG, util.ChaiUtility, testAttributeReplication for 
EntryDN: cn=pwmadmin,dc=pccwglobal,dc=net:pwmLastPwdUpdate 0 up, 1 down, 0 in 
sync
2014-04-23 17:30:41, TRACE, util.ChaiUtility, testAttributeReplication, will 
test the following ldap urls: [ldap://63.220.240.90:389]
2014-04-23 17:30:41, TRACE, provider.JNDIProviderImpl, bind successful as 
cn=admin,dc=pccwglobal,dc=net (0ms)
2014-04-23 17:30:41, TRACE, provider.ChaiProviderFactory, adding 
WatchdogWrapper to provider instance
2014-04-23 17:30:41, TRACE, provider.WatchdogWrapper, checking for user 
password expiration to adjust watchdog timeout
2014-04-23 17:30:41, TRACE, provider.ChaiProviderFactory, adding 
StatisticsWrapper to provider instance
2014-04-23 17:30:41, DEBUG, util.ChaiUtility, testAttributeReplication for 
EntryDN: cn=pwmadmin,dc=pccwglobal,dc=net:pwmLastPwdUpdate 0 up, 1 down, 0 in 
sync
2014-04-23 17:30:43, TRACE, util.ChaiUtility, testAttributeReplication, will 
test the following ldap urls: [ldap://63.220.240.90:389]
2014-04-23 17:30:43, TRACE, provider.JNDIProviderImpl, bind successful as 
cn=admin,dc=pccwglobal,dc=net (0ms)
2014-04-23 17:30:43, TRACE, provider.ChaiProviderFactory, adding 
WatchdogWrapper to provider instance
2014-04-23 17:30:43, TRACE, provider.WatchdogWrapper, checking for user 
password expiration to adjust watchdog timeout
2014-04-23 17:30:43, TRACE, provider.ChaiProviderFactory, adding 
StatisticsWrapper to provider instance
2014-04-23 17:30:43, DEBUG, util.ChaiUtility, testAttributeReplication for 
EntryDN: cn=pwmadmin,dc=pccwglobal,dc=net:pwmLastPwdUpdate 0 up, 1 down, 0 in 
sync
2014-04-23 17:30:45, TRACE, util.ChaiUtility, testAttributeReplication, will 
test the following ldap urls: [ldap://63.220.240.90:389]
2014-04-23 17:30:45, TRACE, provider.JNDIProviderImpl, bind successful as 
cn=admin,dc=pccwglobal,dc=net (0ms)

Original issue reported on code.google.com by pasulapr...@gmail.com on 23 Apr 2014 at 5:54

GoogleCodeExporter commented 9 years ago 
Please ask this question in the forums. It does not seem PWM related, but an 
issue with your configuration.

Original comment by menno.pi...@gmail.com on 23 Apr 2014 at 5:58