You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. (memberOf=cn=pwmadmins,ou=groups,dc=phmbrokers,dc=internal)
2. This search worked from ldapsearch
3. This search worked with stable build that was downloaded
What is the expected output? What do you see instead?
Should have accepted the criteria
What version of PWM are you using?
Latest source - however built 1.7.1 worked fine.. Same LDAP / same query string
worked on 1.7.1 but not latest source
What ldap directory and version are you using?
OpenLDAP
Please paste any error log messages below:
2015-03-24T11:58:53Z, TRACE, provider.JNDIProviderImpl, bind successful as
cn=Manager,dc=phmbrokers,dc=internal (2ms)
2015-03-24T11:58:53Z, TRACE, provider.ChaiProviderFactory, adding
WatchdogWrapper to provider instance
2015-03-24T11:58:53Z, DEBUG, provider.WatchdogWrapper, starting up LDAP Chai
WatchdogWrapper timer thread, 5000ms check frequency
2015-03-24T11:58:53Z, TRACE, provider.WatchdogWrapper, checking for user
password expiration to adjust watchdog timeout
2015-03-24T11:58:53Z, TRACE, provider.ChaiProviderFactory, adding
StatisticsWrapper to provider instance
2015-03-24T11:58:53Z, TRACE, impl.AbstractChaiEntry, error during isValid check
of '(memberOf=cn=pwmadmins,ou=groups,dc=phmbrokers,dc=internal)', error:
(memberOf=cn=pwmadmins,ou=groups,dc=phmbrokers,dc=internal): [LDAP: error code
34 - invalid DN]
2015-03-24T11:59:28Z, DEBUG, provider.WatchdogWrapper, ldap idle timeout
detected, closing ldap connection for ChaiProvider #6 (JNDIProviderImpl), OPEN
ldap://54.183.129.225:389 cn=Manager,dc=phmbrokers,dc=internal
2015-03-24T11:59:28Z, DEBUG, provider.WatchdogWrapper, exiting LDAP Chai
WatchdogWrapper timer thread, no connections requiring monitoring are in use
Original issue reported on code.google.com by [email protected] on 24 Mar 2015 at 12:05
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 24 Mar 2015 at 12:05The text was updated successfully, but these errors were encountered: