The Hooks backend allows hooks to extend a group to dynamically include
members into a group. See hooks.php.dist for an example.
</configdescription>
- <configsection name="params">
- <configswitch name="driver" desc="What backend should we use for Horde
+ <configswitch name="driver" desc="What backend should we use for Horde
Groups?">sql
- <case name="hooks" desc="Hooks"/>
- <case name="kolab" desc="Kolab"/>
- <case name="ldap" desc="LDAP">
+ <case name="hooks" desc="Hooks"/>
+ <case name="kolab" desc="Kolab"/>
+ <case name="ldap" desc="LDAP">
+ <configsection name="params">
<configldap switchname="driverconfig">
<configstring name="gid" desc="The group search key">cn</configstring>
<configstring name="memberuid" desc="Group membership field">
</case>
</configswitch>
</configldap>
- </case>
- <case name="mock" desc="No Groups"/>
- <case name="sql" desc="SQL">
- <configsql switchname="driverconfig" />
- </case>
- </configswitch>
- </configsection>
+ </configsection>
+ </case>
+ <case name="mock" desc="No Groups"/>
+ <case name="sql" desc="SQL">
+ <configsql switchname="driverconfig" />
+ </case>
+ </configswitch>
<configheader>Group Caching</configheader>
<configdescription>Enabling group caching improves performance because the
group backend will only be queried once per session. But it also increases