[prev in list] [next in list] [prev in thread] [next in thread]
List: openldap-software
Subject: uniqueMemberMatch
From: "James Courtney" <Jcourtney () inphonic ! com>
Date: 2003-09-29 23:01:41
[Download RAW message or body]
Does anyone know where to get a detailed description of the behavior of =
each matching rule supported by OpenLDAP? The Admin manual doesn't seem =
to contain such a thing.
I'm trying to understand how uniqueness is enforced in LDAP using the =
groupOfUniqueNames objectclass. Nothing about the schema definition =
indicates that any uniqueness is enforced:
objectclass ( 2.5.6.17 NAME 'groupOfUniqueNames'
DESC 'RFC2256: a group of unique names (DN and Unique =
Identifier)'
SUP top STRUCTURAL
MUST ( uniqueMember $ cn )
MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description =
) )
It must have a uniqueMember attribute which is then indexed using the =
uniqueMemberMatch matching rule:
attributetype ( 2.5.4.50 NAME 'uniqueMember'
DESC 'RFC2256: unique member of a group'
EQUALITY uniqueMemberMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
The only way to enforce uniqueness that I see is if uniqueMemberMatch =
corresponds to a unique index.
Sorry if I'm looking at this strangely or incorrectly but I'm used to =
relational databases and I still haven't quite gotten comfortable =
talking about LDAP yet.
Thanks to all!
Cheers,
Jamey
James Courtney
Software Engineer
InPhonic, Inc.
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>uniqueMemberMatch</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">Does anyone know where to get a detailed description of \
the behavior of each matching rule supported by OpenLDAP? The Admin manual \
doesn't seem to contain such a thing.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">I'm trying to understand how uniqueness is enforced in \
LDAP using the groupOfUniqueNames objectclass. Nothing about the schema \
definition indicates that any uniqueness is enforced:</FONT></P>
<P><FONT SIZE=2 FACE="Arial">objectclass ( 2.5.6.17 NAME 'groupOfUniqueNames'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> DESC \
'RFC2256: a group of unique names (DN and Unique Identifier)'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> SUP top \
STRUCTURAL</FONT>
<BR><FONT SIZE=2 FACE="Arial"> MUST ( \
uniqueMember $ cn )</FONT>
<BR><FONT SIZE=2 FACE="Arial"> MAY ( \
businessCategory $ seeAlso $ owner $ ou $ o $ description ) )</FONT> </P>
<P><FONT SIZE=2 FACE="Arial">It must have a uniqueMember attribute which is then \
indexed using the uniqueMemberMatch matching rule:</FONT> </P>
<P><FONT SIZE=2 FACE="Arial">attributetype ( 2.5.4.50 NAME 'uniqueMember'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> DESC \
'RFC2256: unique member of a group'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> EQUALITY \
uniqueMemberMatch</FONT>
<BR><FONT SIZE=2 FACE="Arial"> SYNTAX \
1.3.6.1.4.1.1466.115.121.1.34 )</FONT> </P>
<P><FONT SIZE=2 FACE="Arial">The only way to enforce uniqueness that I see is if \
uniqueMemberMatch corresponds to a unique index.</FONT> </P>
<P><FONT SIZE=2 FACE="Arial">Sorry if I'm looking at this strangely or incorrectly \
but I'm used to relational databases and I still haven't quite gotten comfortable \
talking about LDAP yet.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Thanks to all!</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Cheers,</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Jamey</FONT>
</P>
<BR>
<P><FONT SIZE=2 FACE="Arial">James Courtney</FONT>
<BR><FONT SIZE=2 FACE="Arial">Software Engineer</FONT>
<BR><FONT SIZE=2 FACE="Arial">InPhonic, Inc.</FONT>
</P>
</BODY>
</HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic