| 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 Hagenbuch <chuck (at) horde (dot) org> |
| Requester | Klaus (dot) Steinberger (at) Physik (dot) Uni-Muenchen (dot) DE |
| Created | 03/15/2008 (58 days ago) |
| Due | |
| Updated | 03/15/2008 (58 days ago) |
| Assigned | |
| Resolved | 03/15/2008 (58 days ago) |
| Attachments | |
| Milestone | v3.2-RC3 |
| Patch |
State ⇒ Resolved
Assigned to Chuck Hagenbuch
Already fixed for the next RC:http://cvs.horde.org/diff.php?r1=1.47.10.27&r2=1.47.10.28&f=framework%2FAuth%2FAuth%2Fldap.php
Patch ⇒
Milestone ⇒ v3.2-RC3
Queue ⇒ Horde Base
Summary ⇒ LDAP auth doesn't work correctly in v3.2-RC3
Type ⇒ Bug
Priority ⇒ 3. High
State ⇒ Unconfirmed
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