Tickets :: [#2250] For LDAP {authentication, group, portal, session} use shared config

6.0.0-beta1

7/14/25

Summary	For LDAP {authentication, group, portal, session} use shared config
Queue	Horde Base
Queue Version	Git master
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	ben (at) , jan (at) horde (dot) org
Requester	kevin_myer (at) iu13 (dot) org
Created	07/12/2005 (7307 days ago)
Due
Updated	06/27/2011 (5131 days ago)
Assigned	10/29/2007 (6468 days ago)
Resolved	06/27/2011 (5131 days ago)
Milestone	Horde 3.2
Patch	No

06/27/2011 04:02:51 PM	Jan Schneider	Comment #6 Assigned to Jan Schneider Taken from Ben Klang State ⇒ Resolved Version ⇒ Git master	Reply to this comment
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.

10/29/2007 02:59:02 AM	Chuck Hagenbuch	Comment #5 Assigned to ben Assigned to Ben Klang State ⇒ Assigned	Reply to this comment
I'm going to assign this to the Bens, hopefully for Horde 3.2. Possible?

07/12/2005 03:19:00 PM	Jan Schneider	Comment #4 State ⇒ Accepted	Reply to this comment
True.

07/12/2005 03:13:40 PM	Chuck Hagenbuch	Comment #3	Reply to this comment
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?

07/12/2005 07:31:04 AM	Jan Schneider	Comment #2 State ⇒ Stalled	Reply to this comment
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.

07/12/2005 01:29:45 AM	kevin_myer (at) iu13 (dot) org	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ For LDAP {authentication, group, portal, session} use shared config Queue ⇒ Horde Base State ⇒ New	Reply to this comment
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.