upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-25 09:09:54 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Definitely, 'dn' and 'distinguishedName' are different things. The

Browse source 
former is a pseudo attribute type used internally by slapd to represent
the distinguished name of an entry and its existance should not be
visible.  The latter is an "abstract" attribute type that is not meant
to exist in practice except as supertype of other dn-valued types.
So, the definition of attribute type 2.5.4.49 has been changed to be
just distinguishedName.  Work on the OPENLDAP_DEVEL_SCHEMA branch will
treat pseudo attributes especially and will not be visible to the
clients.
This commit is contained in:
Julio Sánchez Fernández 1999-07-16 10:39:40 +00:00
parent fd8b582aa9
commit ac49f25f75
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
servers/slapd/schema/core.schema
View file

@ -210,11 +210,17 @@ attribute ( 2.5.4.30 NAME 'supportedApplicationContext'
EQUALITY objectIdentifierMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
# Placed here because others derive from it
# We had a dn definition in slapd.at.conf and Netscape lists both
# names for that OID
# Placed here because others derive from it.
attribute ( 2.5.4.49 NAME ( 'distinguishedName' 'dn' )
# We had a dn definition in slapd.at.conf and Netscape lists both
# names for that OID. This is wrong, 'dn' is used internally in slapd
# as the name of a pseudo-attribute type that contains the
# distinguished name of an entry. On the other hand, the attribute
# type distinguishedName is meant to be an "abstract" type and other
# dn-valued attribute types derive from it. So at most, 'dn' would
# be a subtype of distinguishedName.
attribute ( 2.5.4.49 NAME 'distinguishedName'
EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )