| Request | LDAPMultiPlugins -- bug report -- by Baird Cowan |
| Posted on | Jan 11, 2008 12:31 pm |
| Subscribe |
| Comment by Baird Cowan on Jan 22, 2008 10:22 pm | |
| No nothing more to add. |
|
|
|
| Comment by clint on Jan 22, 2008 6:12 pm | |
|
I am having the same problem with our Plone/LDAPuserfolder enabled sites attempting to authenticate against Novell eDirectory. I cannot isolate the problem specifically to ldapuserfolder yet...but I have noticed less authentication requests when we place a ldapuserfolder inside a plain-vanilla password protected Zope folder in the ZMI, instead of a full-blown plone site. Not sure if this helps. I'd volunteer any assistance if you would like. I'm still trying to get my head around this issue :-( If you have found a solution, work around, or troubleshooting ideas, I would be glad to hear them. |
|
|
|
| Comment by Jens Vagelpohl on Jan 17, 2008 3:34 am | |
|
> After further review I am not sure it's and issue with the plugin or > how the exception is being thrown, and handled. > > I have done some more digging, and from what I can find the reason > that the system locks the password on failed login is that it > attempts a login 6 times. I added a bit of code to /opt/zenoss/ > Products/LDAPUserFolder/LDAPDelegate.py to see how many times that > the connect was being called. line #175 > logger.critical('THISISMETEST') > > I can now see in the event.log in zenoss that every login I see six > of theses messages. > > > I have placed a statement in the LDAPDele Your previous comment was cut off, was there anything else? |
|
|
|
| Comment by Baird Cowan on Jan 16, 2008 7:58 pm | |
| The latest stable releases 2.8 and 1.5 respectively. Sorry for the confusion. |
|
|
|
| Comment by Jens Vagelpohl on Jan 16, 2008 5:21 pm | |
|
I was referring to the LDAPMltiPlugins/LDAPUserFolder version. |
|
|
|
| Comment by Baird Cowan on Jan 16, 2008 5:15 pm | |
|
2.1.1 After further review I am not sure it's and issue with the plugin or how the exception is being thrown, and handled. I have done some more digging, and from what I can find the reason that the system locks the password on failed login is that it attempts a login 6 times. I added a bit of code to /opt/zenoss/Products/LDAPUserFolder/LDAPDelegate.py to see how many times that the connect was being called. line #175 logger.critical('THISISMETEST') I can now see in the event.log in zenoss that every login I see six of theses messages. I have placed a statement in the LDAPDele |
|
|
|
| Comment by Jens Vagelpohl on Jan 16, 2008 4:32 pm | |
|
Could you specify the exact software version you are using? |
|
|
|
| Comment by Baird Cowan on Jan 14, 2008 1:57 pm | |
|
Here is information from the event.log in zenoss. 2008-01-14T08:42:07 CRITICAL event.LDAPDelegate Failure connecting, last attempted server: ldap://server:389 ({'info': 'NDS error: failed authentication (-669)', 'desc': 'Invalid credentials'}) Traceback (most recent call last): File "/opt/zenoss/Products/LDAPUserFolder/LDAPDelegate.py", line 212, in connect , op_timeout=server['op_timeout'] File "/opt/zenoss/Products/LDAPUserFolder/LDAPDelegate.py", line 314, in _connect connection.simple_bind_s(user_dn, user_pwd) |
|
|
|
| Initial Request by Baird Cowan on Jan 11, 2008 12:31 pm | |
| Appears to lock accounts in Novell due to the multiple attempts the module tries in LDAP. Using this with zenoss. And when a user logs in with bad password, it tries over and over until the login has been locked. |
