Overview#

Lightweight Directory Access Protocol (LDAP) Transactions extends the Lightweight Directory Access Protocol (LDAP) to allow clients to relate a number of update operations and have them performed as one unit of interaction, a transaction.

As with distinct update operations, each transaction has atomic, consistency, isolation, and durability properties ACID.

Lightweight Directory Access Protocol (LDAP) Transactions is define din RFC 5805 and is defined as "Experimental"

This extension consists of two extended operations, one control, and one Unsolicited Notification message.

Elements of an LDAP Transaction

• Start Transaction Request/Start Transaction Response is used to obtain a transaction identifier. This identifier is then attached to multiple update operations to indicate that they belong to the transaction using the Transaction Specification Control.
• Transaction Specification Control
• End Transaction Request/End Transaction Response is used to settle (commit or abort) the transaction.
• Aborted Transaction Notice is provided by the server to notify the client that the server is no longer willing or able to process an outstanding transaction.

eDirectory LDAP Transaction#

More Information#

There might be more information for this subject on one of the following:

• EDirectory LDAP Transaction
• LDAP Transactions
• LDAPv3 Grouping of Related Operations
• RFC 5805