Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>LDAP/X.500 defines only <em>group objects</em> which have <em>member attributes</em>, the inverse relation where a user object has a <em>memberof</em> attribute in OpenLDAP can be achieved with the <a href="http://www.openldap.org/doc/admin24/overlays.html#Reverse%20Group%20Membership%20Maintenance" rel="nofollow noreferrer"><code>memberof</code> overlay</a>. NDS/eDir and AD make this happen by magic. LDAP proper does not define dynamic bi-directional member/group objects/attributes. Related to that overlay is the <a href="http://www.openldap.org/doc/admin24/overlays.html#Referential%20Integrity" rel="nofollow noreferrer">refint</a> overlay which helps complete the illusion (and also addresses the mildly irritating problem of a group always requiring at least one member).</p> <p>There are generally two interesting group types to pick, <code>groupOfNames</code> or <code>groupOfUniqueNames</code>, the first one <code>GroupOfNames</code> is suitable for most purposes. The latter, <code>groupOfUniqueNames</code>, has a slightly esoteric feature: it allows the member <a href="https://tools.ietf.org/html/rfc2252#section-6.21" rel="nofollow noreferrer">DN to contain a numeric UID suffix</a>, to preserve uniqueness of members across time should DNs be reassigned to different entities. Neither form enforces unique DNs in the list of members.</p> <p>Other types of groups have distinct purposes (defined by schema and application). A less common group-type object is <a href="http://www.rfc-editor.org/rfc/rfc2256.txt" rel="nofollow noreferrer">RFC 2256</a> <em>roles</em> (<code>organizationalRole</code> type, with <code>roleOccupant</code> attribute), this is implicitly used for role-based access control, but is otherwise similar to the other group types (thanks to <a href="https://stackoverflow.com/users/207421/ejp">EJP</a> for the tip).</p> <p>The <code>posixGroup</code> type represents the conventional unix groups, identified by a <code>gidNUmber</code> and listing <code>memberUid'</code>s. It is not a general purpose group object in the DIT, it's up to the application (i.e. the LDAP client layer) to implement/observe it.</p> <p>When it comes to user accounts, account object-types should not be thought of as exclusive, each type typically adds attributes to a user object in a compatible way (though an <code>objectClass</code> <em>can</em> be exclusive if it's <em>structural</em>, that's not something you'll often have to worry about generally). </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload