6.0.0-alpha12
6/12/25

[#13243] Ldap group bad filter if attrisdn is checked
Summary Ldap group bad filter if attrisdn is checked
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Duplicate
Priority 2. Medium
Owners
Requester gerard.breiner (at) ias (dot) u-psud (dot) fr
Created 06/04/2014 (4026 days ago)
Due 06/04/2014 (4026 days ago)
Updated 06/04/2014 (4026 days ago)
Assigned
Resolved 06/04/2014 (4026 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
06/04/2014 03:02:33 PM Jan Schneider State ⇒ Duplicate
 
06/04/2014 02:15:47 PM gerard (dot) breiner (at) ias (dot) u-psud (dot) fr Comment #1
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Ldap group bad filter if attrisdn is checked
Due ⇒ 06/04/2014
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ Yes
New Attachment: conf.xml Download
Reply to this comment
Hello,
I know there already is a ticket 12128 but it  seems to be stalled (no 
answers to the workaround I submitted.

For remind... We get an exception when we are in the kronolith 
interface if attrisdn is checked in the tab "Group? 
admin/config/config.php?app=horde.

The error message is :
Bad search filter Parameters:
Base: dc=mydomain,dc=fr Filter: (&(objectclass=)(=milo))

The exception is rised in Horde_Ldap where findUserDN() is defined and 
which is called by listGroups() in Horde Horde_Group_Ldap
The problem is that findUserDN need uid and filter but theses 
parameters are not defined in the group section of 
horde/config/conf.xml.  I added them and that resolved this issue on 
my platform horde 5.1.5.

Could you please tell me your feelings about  my proposal.

Here is in attachment the conf.xml modified.

Best regards.

Gérard Breiner

Saved Queries