480
Chapter 23: Managing LDAP Directories
Entry
The basic information object of LDAP is the
entry
. An entry is composed of one or more
attributes
. Entries are subject to content rules defined by the directory
schema
(see
“Schema”
on page 481
).
Each node, not just the terminal nodes, of an LDAP directory is an entry. In the preceding
figures, each item is an entry. For example, in the first diagram, both USA and Ferrari are entries.
The USA entry’s attributes could include a Language attribute, and the Ferrari entry could
include an entry for the chief executive officer.
Attribute
An LDAP directory entry consists of one or more attributes. Attributes have
types
and
values
. The
type determines the information that the values can contain. The type also specifies how the value
is processed. For example, the type determines whether an attribute can have multiple values. The
mail attribute type, which contains an e-mail address, is multivalued so you can store multiple e-
mail addresses for one person.
Some commonly-used attribute types have short keyword type names. Often these correspond to
longer type names, and the two names can be used interchangeably. The following table lists
common attribute type keywords used in LDAP directories:
At the time this chapter was written, Netscape provided a list of standard Attribute names on its
website, at:
http://developer.netscape.com/docs/manuals/directory/schema2/41/contents.htm
For more information, see
“Attribute type” on page 482
.
Distinguished name (DN)
An entry’s
distinguished name
uniquely identifies it in the directory. A DN is made up of
relative
distinguished names
(RDNs). An RDN identifies the entry among the children of its parent entry.
For example, in the first figure in
“About LDAP”
, the RDN for the Ferrari entry is “o=Ferrari”.
Keyword
Long name
Comment
c
CountryName
st
stateOrProvinceName
l
LocalityName
typically, city, but can be any geographical unit
street
StreetAddress
o
OrganizationName
ou
OrganizationalUnitName
cn
CommonName
typically, first and last name
sn
SurName
dc
domaincomponent
e-mail address
Summary of Contents for COLDFUSION MX 61-DEVELOPING COLDFUSION MX
Page 1: ...Developing ColdFusion MX Applications...
Page 22: ...22 Contents...
Page 38: ......
Page 52: ...52 Chapter 2 Elements of CFML...
Page 162: ......
Page 218: ...218 Chapter 10 Writing and Calling User Defined Functions...
Page 250: ...250 Chapter 11 Building and Using ColdFusion Components...
Page 264: ...264 Chapter 12 Building Custom CFXAPI Tags...
Page 266: ......
Page 314: ...314 Chapter 14 Handling Errors...
Page 344: ...344 Chapter 15 Using Persistent Data and Locking...
Page 349: ...About user security 349...
Page 357: ...Security scenarios 357...
Page 370: ...370 Chapter 16 Securing Applications...
Page 388: ...388 Chapter 17 Developing Globalized Applications...
Page 408: ...408 Chapter 18 Debugging and Troubleshooting Applications...
Page 410: ......
Page 426: ...426 Chapter 19 Introduction to Databases and SQL...
Page 476: ...476 Chapter 22 Using Query of Queries...
Page 534: ...534 Chapter 24 Building a Search Interface...
Page 556: ...556 Chapter 25 Using Verity Search Expressions...
Page 558: ......
Page 582: ...582 Chapter 26 Retrieving and Formatting Data...
Page 668: ......
Page 734: ...734 Chapter 32 Using Web Services...
Page 760: ...760 Chapter 33 Integrating J2EE and Java Elements in CFML Applications...
Page 786: ...786 Chapter 34 Integrating COM and CORBA Objects in CFML Applications...
Page 788: ......