PingDS 7.5.1

subentry

Subentries are analogous to operational attributes in that they are used by the server for administrative purposes. Examples include password policies, entries for allocating collective attributes, and the entry exposing directory schema.

Unlike entries in the server-specific configuration backend, Subentries are present in and replicated with user data. Modifying subentries nevertheless requires the subentry-write administrative privilege.

Names

subentry

Origin

RFC 3672

Description

LDAP Subentry class

Superior classes

top

OID

2.5.17.0

Required attributes

cn, objectClass, subtreeSpecification

Schema file

00-core.ldif

Class type

STRUCTURAL: for structural specification of the DIT. Entries have only one structural object class superclass chain.