Triggers and The Directory Administrative Authority Model

The following schema elements are proposed.

attributetype ( 1.2.6.1.4.1.18060.1.1.1.3.25 NAME 'prescriptiveTrigger'
    DESC 'Trigger specification that applies to a set of entries'
    EQUALITY directoryStringFirstComponentMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.59
    USAGE directoryOperation )

attributetype ( 1.2.6.1.4.1.18060.1.1.1.3.26 NAME 'entryTrigger'
    DESC 'Trigger specification that applies to a single entry'
    EQUALITY directoryStringFirstComponentMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.59
    USAGE directoryOperation )

attributetype ( 1.2.6.1.4.1.18060.1.1.1.3.27 NAME 'triggerSubentries'
    DESC 'Used to track subentries associated with a trigger area which an entry falls under'
    SUP distinguishedName
    EQUALITY distinguishedNameMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
    NO-USER-MODIFICATION
    USAGE directoryOperation ))

objectclass ( 1.2.6.1.4.1.18060.1.1.1.3.28 NAME 'triggerSubentry'
    DESC 'Used to track a subentry associated with trigger areas'
    AUXILIARY
    MUST prescriptiveTrigger )

TODO: Add support for Trigger Schemes. This means an attribute like triggerScheme per Trigger Specific Entry with currently one possible value "basicTriggerScheme".

References

RFC 3672 Subentries in the Lightweight Directory Access Protocol (LDAP)

Page Operations

Browse Space

References