[#2250] For LDAP {authentication, group, portal, session} use shared config
Summary For LDAP {authentication, group, portal, session} use shared config
Queue Horde Base
Queue Version HEAD
Type Enhancement
State Assigned
Priority 1. Low
Owners Ben Chavet <ben (at) horde (dot) org>, Ben Klang <ben (at) alkaloid (dot) net>
Requester kevin_myer (at) iu13 (dot) org
Created 07/11/2005 (1037 days ago)
Due
Updated 10/28/2007 (198 days ago)
Assigned 10/28/2007 (198 days ago)
Resolved 07/12/2005 (1036 days ago)
Attachments
Milestone Horde 3.2
Patch

History
10/28/2007 Chuck Hagenbuch Comment #5
Assigned to Ben Klang
State ⇒ Assigned
Assigned to Ben Chavet		 Reply to this comment
I'm going to assign this to the Bens, hopefully for Horde 3.2. Possible?
07/12/2005 Jan Schneider Comment #4
State ⇒ Accepted		 Reply to this comment
True.
07/12/2005 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 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/11/2005 kevin_myer (at) iu13 (dot) org Comment #1
Type ⇒ Enhancement
Summary ⇒ For LDAP {authentication, group, portal, session} use shared config
Queue ⇒ Horde Base
Priority ⇒ 1. Low
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.