6.0.0-git
2021-01-18

[#6450] LDAP auth doesn't work correctly in v3.2-RC3
Summary LDAP auth doesn't work correctly in v3.2-RC3
Queue Horde Base
Queue Version HEAD
Type Bug
State Resolved
Priority 3. High
Owners chuck (at) horde (dot) org
Requester Klaus.Steinberger (at) physik (dot) uni-muenchen (dot) de
Created 2008-03-15 (4692 days ago)
Due
Updated 2008-03-15 (4692 days ago)
Assigned
Resolved 2008-03-15 (4692 days ago)
Milestone v3.2-RC3
Patch No

History
2008-03-15 18:51:25 Chuck Hagenbuch Comment #2
Assigned to Chuck Hagenbuch
State ⇒ Resolved
Reply to this comment
2008-03-15 18:49:51 Klaus (dot) Steinberger (at) physik (dot) uni-muenchen (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Summary ⇒ LDAP auth doesn't work correctly in v3.2-RC3
Queue ⇒ Horde Base
Milestone ⇒ v3.2-RC3
Patch ⇒ No
Reply to this comment
LDAP Auth does not work in RC3



The errore message is "Empty Result"



A trace with wireshark shows the following filter in the search request:



(&(uid=username)(objectClass=username))



The parameter is set the following way:

$conf['auth']['params']['objectclass'] = array('posixAccount');



An "echo $filter" inside _getParamFilter reveals the following output:



(objectClass=)



When I set the parameter the following way:



$conf['auth']['params']['objectclass'] = array('posixAccount', 'User');



The authentication works, the filter is set correctly with both 
objectClasses (User is correct for our Novell Edirectory).



So it looks like there is some false handling of this parameter.



Sincerly,

Klaus Steinberger




Saved Queries