Fri, 10 Apr 2026 06:14:16 +0000 https://bugs.horde.org/ticket/2250 For LDAP {authentication, group, portal, session} use shared config In much the same manner that most database configs can use a horde_defaults value (which reuse many of the base database configuration items and provides a default table name for each config area), expand all LDAP-related configuration items to follow this model. basedn, hostpec, port, bindn, and password could be reused and default RDNs be specified, but configurable for things like People, Groups, Sessions, etc. Tue, 12 Jul 2005 01:29:45 +0000 https://bugs.horde.org/ticket/2250#t9674 The problem is that such a configuration can't be introduced without breaking BC because we need a new configuration tag. Stalled until Horde 4. Tue, 12 Jul 2005 07:31:04 +0000 https://bugs.horde.org/ticket/2250#t9679 We could introduce it in Horde, though. That way Horde configs can use it, and other apps can reference it in config files like sources.php - they just can't rely on it in driver code. Right? Tue, 12 Jul 2005 15:13:40 +0000 https://bugs.horde.org/ticket/2250#t9688 True. Tue, 12 Jul 2005 15:19:00 +0000 https://bugs.horde.org/ticket/2250#t9690 I'm going to assign this to the Bens, hopefully for Horde 3.2. Possible? Mon, 29 Oct 2007 02:59:02 +0000 https://bugs.horde.org/ticket/2250#t38216 This has been implemented in Horde 4. It's not used in all places yet, but the basis is there, so it can be added without BC breakage. Mon, 27 Jun 2011 16:02:51 +0000 https://bugs.horde.org/ticket/2250#t65883