Novell EDIRECTORY 8.8 SP3, Administration Manual, Page: 345 / 634

Understanding LDAP Services for Novell eDirectory 345
n
ov
do
cx (e
n)
11
Ju
ly 20
08
Usage Examples
The following are examples of the string representations of extensible match search filter that are
supported in eDirectory 8.7.3 onwards.
(o:dn:=Ace Industry)
This example illustrates the use of the :dn notation. The attributes of an entry’s distinguished name
should be considered part of the entry when evaluating the match. It denotes an equality match.
(:dn:2.4.8.10:=Dino)
This example is a filter that should be applied to any attribute of an entry. Attributes contained in the
DN with the matching rule 2.4.8.10 should also be considered.
The following are some examples of the string representation of extensible match search filter that
are
not supported in eDirectory 8.7.3:
(cn:1.2.3.4.5:=John Smith)
This example illustrates a filter that specifies the attributes type cn and value John Smith. It
mandates that the match should be performed by the directory server according to the matching rule
identified by the oid 1.2.3.4.5.
(sn:dn:2.4.6.8.10:=Barbara Jones)
This example illustrates the use of the :dn notation to indicate that matching rule 2.4.6.8.10 should
be used when making comparisons, and that the attributes of an entry’s distinguished name should
be considered part of the entry when evaluating the match.
13.5 LDAP Transactions
eDirectory LDAP server supports clubbing of multiple update operations into a single atomic
operation - also called a transaction. The support for transactions over LDAP in eDirectory is based
on two Internet specifications –
LDAP transactions (http://mirrors.isc.org/pub/
www.watersprings.org/pub/id/draft-zeilenga-ldap-txn-05.txt) and LDAPv3: Grouping of Related
Operations (http://mirrors.isc.org/pub/www.watersprings.org/pub/id/draft-zeilenga-ldap-grouping-
05.txt)
.
LDAP transactions allow an LDAP application to send several LDAP update operations (add,
modify, delete, rename) as a group and then commit or abort this whole group of operations.
There are few entities which figure in the context of LDAP transactions:
Š
CreateGroupingRequest ( 2.16.840.1.113719.1.27.103.1 ) – This is LDAP extended operation
which allows grouping of related operations. The extended operation carries a value –
createGroupType which identifies the type of grouping requested. For LDAP transactions, the
grouping type is transactionGroupingType. ( 2.16.840.1.113719.1.27.103.7)
Š
CreateGroupingResponse ( 2.16.840.1.113719.1.27.103.1 ) – This is the response of the LDAP
server to the createGroupingRequest and contains 2 response fields – groupCookie and an
optional createGroupValue.
Š
GroupingControl ( 2.16.840.1.113719.1.27.103.7 ) - This is used to indicate association of an
operation to a grouping via the groupCookie which is the value carried by this control.