3.1.1.5.5.1.2 Deleted-Object Requirements

The following requirements apply to deleted-objects except the Deleted Objects container (which is considered a deleted-object and never an existing-object or a recycled-object if the Recycle Bin optional feature is enabled):

  • The isDeleted attribute is set to TRUE on deleted-objects.

  • The isRecycled attribute is not present.

  • The deleted-object retains all of the attributes of the original object except for the attributes objectCategory and sAMAccountType.

  • The deleted-object does not have descendant objects.

  • The deleted-object remains in the database and is available for outbound replication for at least the deleted-object lifetime interval (see section 6.1.1) after its deletion.

  • If a deleted-object has linked attribute values, then those attribute values are retained. For details, see LDAP_SERVER_SHOW_DEACTIVATED_LINK_OID (section 3.1.1.3.4.1.25).

  • If any NC replicas contain other objects with linked attribute values referencing deleted-objects, then those attribute values on those objects are retained. In other words, when an object is deleted and transformed into a deleted-object, any linked attribute values on other objects referencing it are not removed. For details, see LDAP_SERVER_SHOW_DEACTIVATED_LINK_OID (section 3.1.1.3.4.1.25).

  • If any NC replicas contain other objects with nonlinked attribute values referencing a deleted-object, then those attribute values on those objects are retained. In other words, when an object is deleted and transformed into a deleted-object, any nonlinked attribute values on other objects referencing it are not removed.

  • Except as described in section 3.1.1.5.5.6, deleted-objects exist only in the Deleted Objects container of an NC.

  • Except as described in section 3.1.1.5.5.6, deleted-objects have "delete-mangled RDNs".

  • A protected object cannot be deleted and transformed into a deleted-object (see Protected Objects in section 3.1.1.5.5.3).

The following requirements apply to the Deleted Objects container when it is a deleted-object:

  • The isDeleted attribute is set to TRUE.

  • The isRecycled attribute is not present.

  • The Deleted Objects container always remains in the database and is available for outbound replication.

  • The Deleted Objects container does not have a "delete-mangled RDN".

Note especially that many of the restrictions specified in this section on other deleted-objects pertaining to attribute values do not apply to the Deleted Objects container.