[Tickets #9762] Re: attrisdn in the Groups LDAP Setup does not work?
bugs at horde.org
bugs at horde.org
Fri Apr 1 09:24:52 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9762
------------------------------------------------------------------------------
Ticket | 9762
Updated By | Klaus.Steinberger at Physik.Uni-Muenchen.DE
Summary | attrisdn in the Groups LDAP Setup does not work?
Queue | Horde Base
Version | 4.0-RC2
Type | Bug
State | Assigned
Priority | 2. Medium
Milestone | 4.1
Patch |
Owners | Jan Schneider
------------------------------------------------------------------------------
Klaus.Steinberger at Physik.Uni-Muenchen.DE (2011-04-01 09:24) wrote:
> Such a setup didn't work with Horde 3 either, unless I'm missing
> something. As far as I can see, Horde 3 only supported a single,
> fixed parent DN for expanding simple user names to full DNs in the
> LDAP group driver.
Yes, but I wrote a patch for this and and a bug report against horde
3, but it is was probably not accepted.
> To support your setup, we need to do another DN lookup to find the user's DN.
> Alternatively, you could of course full DNs as user names in Horde.
Hmm, but this would have consequences, at least some complicated
scripting to convert our existing production database.
More information about the bugs
mailing list