Tickets :: [#9110] Option to specify LDAP objectclass is lost

Summary	Option to specify LDAP objectclass is lost
Queue	Horde Base
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	6/24/10 (5769 days ago)
Due
Updated	9/20/10 (5681 days ago)
Assigned
Resolved	9/20/10 (5681 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/20/2010 05:56:22 PM	Jan Schneider	Assigned to Jan Schneider Taken from Ben Klang State ⇒ Resolved

06/28/2010 11:15:00 PM	Michael Slusarz	Comment #2	Reply to this comment
Looks like it was removed in this commit: commit 9cb448eaeffa8c43e2a6256d57a425b66ce6220c Author: Ben Klang <ben@alkaloid.net> AuthorDate: Tue Jun 8 13:38:54 2010 -0400 Commit: Ben Klang <ben@alkaloid.net> CommitDate: Tue Jun 8 15:36:54 2010 -0400 Framework: First pass at fixing searchdn/writedn support

06/24/2010 01:02:25 PM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Assigned to Ben Klang Queue ⇒ Horde Base Summary ⇒ Option to specify LDAP objectclass is lost Type ⇒ Bug State ⇒ Assigned	Reply to this comment
The option to specify an objectclass instead of a complete filter string got lost during the LDAP configuration refactoring. If this wasn't intended, it should be re-added.