This document is intended to clarify the Horde Group API, and to provide a solid target for applications to move toward for Horde4. Motivation for this document was spurred from the conversation between the Bens on IRC regarding the "proper" way to handle groups with LDAP.
In its simplest terms a group consists of an ID and a Name. The ID is unique to that group and is unchanging. The name is a human-friendly name that can be changed as desired. The source and/or format of the group ID should not be of concern to the application using it, and should always be obtained/modified/stored through the group API calls. The group ID is the only acceptable method as to refer to a group, as it is guaranteed to be unique (uniqueness being the job of the driver). The group name is strictly for interface use.
Horde 4 will deviate from Horde 3 in these key ways:
This is the class that does the work of reading from/saving to the group storage backend.
Creates a new group and returns a new group ID.
Changes the name of a group without affecting its membership list
Removes a group from the groups system permanently.
Boolean: Check if a group exists in the system.
Returns a group name.
Returns an array of all groups, in the format gid => name.
Get a list of every user that is a part of this group ONLY.
If $recurse is true then also check member groups' user lists.
Returns an array of group IDs representing the user's membership
Add a user to a group.
Remove a user from a group.
Returns a list of group IDs that match the name (substring search?)