dn.htm 8.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293
  1. <!-- --- BEGIN COPYRIGHT BLOCK ---
  2. This Program is free software; you can redistribute it and/or modify it under
  3. the terms of the GNU General Public License as published by the Free Software
  4. Foundation; version 2 of the License.
  5. This Program is distributed in the hope that it will be useful, but WITHOUT
  6. ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
  7. FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
  8. You should have received a copy of the GNU General Public License along with
  9. this Program; if not, write to the Free Software Foundation, Inc., 59 Temple
  10. Place, Suite 330, Boston, MA 02111-1307 USA.
  11. In addition, as a special exception, Red Hat, Inc. gives You the additional
  12. right to link the code of this Program with code not covered under the GNU
  13. General Public License ("Non-GPL Code") and to distribute linked combinations
  14. including the two, subject to the limitations in this paragraph. Non-GPL Code
  15. permitted under this exception must only link to the code of this Program
  16. through those well defined interfaces identified in the file named EXCEPTION
  17. found in the source code files (the "Approved Interfaces"). The files of
  18. Non-GPL Code may instantiate templates or use macros or inline functions from
  19. the Approved Interfaces without causing the resulting work to be covered by
  20. the GNU General Public License. Only Red Hat, Inc. may make changes or
  21. additions to the list of Approved Interfaces. You must obey the GNU General
  22. Public License in all respects for all of the Program code and other code used
  23. in conjunction with the Program except the Non-GPL Code covered by this
  24. exception. If you modify this file, you may extend this exception to your
  25. version of the file, but you are not obligated to do so. If you do not wish to
  26. provide this exception without modification, you must delete this exception
  27. statement from your version and license this file solely under the GPL without
  28. exception.
  29. Copyright (C) 2001 Sun Microsystems, Inc. Used by permission.
  30. Copyright (C) 2005 Red Hat, Inc.
  31. All rights reserved.
  32. --- END COPYRIGHT BLOCK --- -->
  33. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  34. <HTML>
  35. <HEAD>
  36. <TITLE></TITLE>
  37. <META NAME="GENERATOR" CONTENT="Mozilla/3.0b6Gold (WinNT; I) [Netscape]">
  38. </HEAD>
  39. <BODY>
  40. <P><A NAME="1001595"></A></P>
  41. <P><A NAME="1001596"></A></P>
  42. <P><A NAME="996824"></A></P>
  43. <H1>Distinguished Names</H1>
  44. <P><A NAME="1017708"></A>Distinguished
  45. Names (DNs) are the string representation for entry names in the Directory
  46. Server database. You use DNs to name entries when you add entries to the
  47. directory, add members to groups, etc..</P>
  48. <P><A NAME="1017709"></A>A DN can consist of virtually any attributes you
  49. wish to use. The only caveat is that if schema checking is turned on, then
  50. the attributes must be recognized by the Directory Server (if you do not
  51. know whether schema checking is turned on in the server, contact your directory
  52. manager, or consult the <I>Netscape Directory Server Administrator's Guide</I>
  53. for more information).</P>
  54. <P><A NAME="1017710"></A>Traditionally, a DN consists of:</P>
  55. <UL>
  56. <P><A NAME="1017711"></A></P>
  57. <LI>A common name followed by<A NAME="1017712"></A></LI>
  58. <LI>a list of regional or organizational attributes followed by<A NAME="1017713"></A></LI>
  59. <LI>a country designation.</LI>
  60. </UL>
  61. <P><A NAME="1017714"></A>This string of identifying attributes uniquely
  62. locates the entry within your Directory Server database. If you choose,
  63. you can also use this naming structure to uniquely identify your entries
  64. within the global directory tree as defined in the X.500 standard.</P>
  65. <P><A NAME="1017715"></A>Because a DN represents a path through the directory
  66. tree, the DN components are order-dependent. For example, the following
  67. DNs do not represent the same entry:</P>
  68. <P><A NAME="1017716"></A></P>
  69. <PRE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cn=Ralph Swenson, ou=Accounting, o=Example Corp, c=US
  70. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cn=Ralph Swenson, o=Example Corp, ou=Accounting, c=US
  71. </PRE>
  72. <P><A NAME="Distinguished Name syntax"></A><A NAME="1017717"></A></P>
  73. <H2>Distinguished Name syntax</H2>
  74. <P><A NAME="1017718"></A>The traditional syntax for a DN string representation
  75. is as follows:</P>
  76. <P><A NAME="1017719"></A></P>
  77. <UL>
  78. <PRE>cn=<I>common name</I>, [street=<I>address</I>, l=<I>locality</I>, st = <I>state or province</I>,
  79. ou=<I>organizational unit</I>, o=<I>organization</I>], c=<I>country name</I>
  80. </PRE>
  81. </UL>
  82. <P><A NAME="1017720"></A>Generally a DN begins with a specific common name,
  83. and proceeds with increasingly broader areas of identification until the
  84. country name is specified. Note, however, that the actual DN attributes
  85. you use, and the order in which you choose to specify them, is up to you
  86. and how you want to organize your database. The only real requirement is
  87. that DN attributes must be separated by a comma (,) and can optionally
  88. use a space ( ) following the separator.</P>
  89. <P><A NAME="Distinguished Name attributes"></A><A NAME="1017721"></A></P>
  90. <H2>Distinguished Name attributes</H2>
  91. <P><A NAME="1017792"></A>The various standard attributes that comprise
  92. a DN are as follows:</P>
  93. <TABLE BORDER=2 >
  94. <CAPTION></CAPTION>
  95. <TR>
  96. <TH><A NAME="1017730"></A><B>Attribute</B></TH>
  97. <TH><A NAME="1017732"></A><B>Name</B></TH>
  98. <TH><A NAME="1017734"></A><B>Definition</B></TH>
  99. </TR>
  100. <TR>
  101. <TD><A NAME="1017736"></A>c</TD>
  102. <TD><A NAME="1017738"></A>country</TD>
  103. <TD><A NAME="1017740"></A>Identifies the name of the country under which
  104. the entry resides. For example,
  105. <UL>
  106. <P><A NAME="1017741"></A></P>
  107. <LI>c=US<A NAME="1017742"></A></LI>
  108. <LI>c=GB</LI>
  109. </UL>
  110. </TD>
  111. </TR>
  112. <TR>
  113. <TD><A NAME="1017744"></A>cn</TD>
  114. <TD><A NAME="1017746"></A>common name</TD>
  115. <TD><A NAME="1017748"></A>Required attribute that identifies the person
  116. or object defined by the entry. For example:
  117. <UL>
  118. <P><A NAME="1017749"></A></P>
  119. <LI>cn=Wally Henderson<A NAME="1017750"></A></LI>
  120. <LI>cn=Database Administrators<A NAME="1017751"></A></LI>
  121. <LI>cn=printer3b</LI>
  122. </UL>
  123. </TD>
  124. </TR>
  125. <TR>
  126. <TD><A NAME="1017753"></A>l</TD>
  127. <TD><A NAME="1017755"></A>locality</TD>
  128. <TD><A NAME="1017757"></A>Identifies the locality in which the entry resides.
  129. The locality could be a city, county, township, or other geographic region.
  130. For example:
  131. <UL>
  132. <P><A NAME="1017758"></A></P>
  133. <LI>l=Tucson<A NAME="1017759"></A></LI>
  134. <LI>l=Pacific Northwest<A NAME="1017760"></A></LI>
  135. <LI>l=Anoka County</LI>
  136. </UL>
  137. </TD>
  138. </TR>
  139. <TR>
  140. <TD><A NAME="1017762"></A>o</TD>
  141. <TD><A NAME="1017764"></A>organization</TD>
  142. <TD><A NAME="1017766"></A>Identifies the organization in which the entry
  143. resides. For example:
  144. <UL>
  145. <P><A NAME="1017767"></A></P>
  146. <LI>o=Netscape Communications Corp<A NAME="1017768"></A></LI>
  147. <LI>o=Public Power &amp; Gas</LI>
  148. </UL>
  149. </TD>
  150. </TR>
  151. <TR>
  152. <TD><A NAME="1017770"></A>ou</TD>
  153. <TD><A NAME="1017772"></A>organizational unit</TD>
  154. <TD><A NAME="1017774"></A>Identifies a unit within the organization. For
  155. example:
  156. <UL>
  157. <P><A NAME="1017775"></A></P>
  158. <LI>ou=Sales<A NAME="1017776"></A></LI>
  159. <LI>ou=Manufacturing</LI>
  160. </UL>
  161. </TD>
  162. </TR>
  163. <TR>
  164. <TD><A NAME="1017778"></A>st</TD>
  165. <TD><A NAME="1017780"></A>state or province name</TD>
  166. <TD><A NAME="1017782"></A>Identifies the state or province in which the
  167. entry resides. For example:
  168. <UL>
  169. <P><A NAME="1017783"></A></P>
  170. <LI>st=Iowa<A NAME="1017784"></A></LI>
  171. <LI>st=British Columbia</LI>
  172. </UL>
  173. </TD>
  174. </TR>
  175. <TR>
  176. <TD><A NAME="1017786"></A>street</TD>
  177. <TD><A NAME="1017788"></A>street address</TD>
  178. <TD><A NAME="1017790"></A>Identifies the street address at which the entry
  179. resides. For example:
  180. <UL>
  181. <P><A NAME="1017791"></A></P>
  182. <LI>street=494 Rice Creek Terrace</LI>
  183. </UL>
  184. </TD>
  185. </TR>
  186. </TABLE>
  187. <TABLE>
  188. <TR>
  189. <TD></TD>
  190. </TR>
  191. </TABLE>
  192. <P><A NAME="Distinguished Name examples"></A><A NAME="1017793"></A></P>
  193. <H2>Distinguished Name examples</H2>
  194. <P><A NAME="1017794"></A>The following are some examples of DNs:</P>
  195. <P><A NAME="1017795"></A></P>
  196. <UL>
  197. <PRE>cn=Wally Henderson,ou=Product Development,o=Example Corp,st=Minnesota,c=US
  198. </PRE>
  199. </UL>
  200. <P><A NAME="1017796"></A></P>
  201. <UL>
  202. <PRE>cn=Retch Sweeny, ou=Product Test, o=Example Corp, st=Michigan, c=US
  203. </PRE>
  204. </UL>
  205. <P><A NAME="1017797"></A></P>
  206. <UL>
  207. <PRE>cn=printer3b, l=room 308, o=Example Corp, c=US
  208. </PRE>
  209. </UL>
  210. <P><A NAME="997436"></A></P>
  211. </BODY>
  212. </HTML>