| 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 | 3/15/08 (6681 days ago) |
| Due | |
| Updated | 3/15/08 (6681 days ago) |
| Assigned | |
| Resolved | 3/15/08 (6681 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | v3.2-RC3 |
| Patch | No |
Assigned to Chuck Hagenbuch
State ⇒ Resolved
http://cvs.horde.org/diff.php?r1=1.47.10.27&r2=1.47.10.28&f=framework%2FAuth%2FAuth%2Fldap.php
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ LDAP auth doesn't work correctly in v3.2-RC3
Queue ⇒ Horde Base
Milestone ⇒ v3.2-RC3
Patch ⇒ No
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