[Tickets #12128] Re: Bad search filter ldap Groups

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12128
------------------------------------------------------------------------------
  Ticket             | 12128
  Updated By         | gerard.breiner at ias.u-psud.fr
  Summary            | Bad search filter ldap Groups
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Jan Schneider
------------------------------------------------------------------------------


gerard.breiner at ias.u-psud.fr (2014-05-06 08:55) wrote:



After having thought  about this issue, I realized that there is  
nothing to change into findUserDN(). This function are not in cause  
and does what she has to do which is to return the DN user.
But when we call from   the Horde group system Horde/Group/Ldap.php via
listGroups() the uid parameter is missed.
So I added the line $conf['group']['params']['uid'] = 'uid'; in  
myhorde/config/conf.php and conf.xml.

This time I have no longer the message 'bad filter' but I get the  
error message

DN for user webadm not found

So I look again at listGroups() in Horde/Group/Ldap.php and try to replace :
$user =  $this->_ldap->findUserDN($user);
by
$user =  Horde_ldap::findUserDN($user);

This time things are better but there is still something bad with the  
filter, in fact, in the interface kronolith I get the message :
Bad search filter Parameters: Base: dc=ias.u-psud,dc=fr Filter:  
(cn=**) Scope: sub.
Maybe it should be cn=* I suppose.

An idea ? Thanks in advance.

Best regards.

Gérard Breiner