Home
last modified time | relevance | path

Searched refs:DN (Results 1 – 25 of 179) sorted by relevance

12345678

/netbsd/external/bsd/openldap/dist/tests/scripts/
H A Dtest026-dn68 DN="OU=Sales+CN=J. Smith,DC=example,DC=net"
72 "(member=$DN)" >> $SEARCHOUT 2>&1
85 "(member=$DN)" \
95 DN="dc=example,dc=com"
99 "(uniqueMember=$DN)" >> $SEARCHOUT 2>&1
108 DN="dc=example,dc=com#'001000'B"
112 "(uniqueMember=$DN)" >> $SEARCHOUT 2>&1
121 DN="dc=example,dc=com#'1000'B"
125 "(uniqueMember=$DN)" >> $SEARCHOUT 2>&1
134 DN="dc=example,dc=com"
[all …]
H A Dtest032-chain156 DN="cn=Mark Elliot,ou=Alumni Association,ou=People,$BASEDN"
157 echo "Comparing \"$DN\" on server $n..."
158 $LDAPCOMPARE -H $URI "$DN" "cn:Mark Elliot" \
168 DN="ou=Other,$BASEDN"
169 echo "Comparing \"$DN\" on server $n with manageDSAit control..."
170 $LDAPCOMPARE -H $URI -M "$DN" "ou:Other" \
/netbsd/external/bsd/openldap/dist/tests/data/
H A Ddn.out11 description: RFC 1779 compliant DN string representation
16 description: RFC 2253 compliant DN string representation
85 only DN portion
86 description: #'1'B // empty "" DN
98 cn: Should Parse as DN
196 only DN portion
197 description: #'1'B // empty "" DN
212 only DN portion
213 description: #'1'B // empty "" DN
228 only DN portion
[all …]
H A Dtest-dn.ldif11 description: RFC 2253 compliant DN string representation
16 # at least one member must be present; thus we use the entry's DN
18 # specific DN forms
33 description: "member" values contain specific DN forms;
37 description: "seeAlso" DN string representations used above.
178 description: RFC 1779 compliant DN string representation
216 # Other DN-related syntaxes
231 description: #'1'B // empty "" DN
232 description: #'0010'B // empty "" DN with leading '0's
233 description: dc=example,dc=com#'1000'B // with DN portion
[all …]
/netbsd/external/bsd/openldap/dist/doc/guide/admin/
H A Dsasl.sdf152 associated DN:
159 LDAP DN format. Or alternatively, the authentication DN could be
214 DN}} of the form
219 authentication request DN would be:
268 authentication request DN to user's DN.
371 user's {{authentication DN}}.
379 map an authentication request DN to a user's authentication DN.
392 string produces a DN, the entry named by this DN need not be held
505 authentication request DN.
552 the access of the new authorization DN.
[all …]
H A Daccess-control.sdf77 qualifiers select entries by DN:
81 > to dn.<scope-style>=<DN>
96 under the DN (but not the entry named by the DN).
171 dn.<scope-style>=<DN>|Users within scope of a DN
174 The DN specifier behaves much like <what> clause DN specifiers.
415 qualifiers select entries by DN:
419 > to dn.<scope-style>=<DN>
434 under the DN (but not the entry named by the DN).
509 dn.<scope-style>=<DN>|Users within scope of a DN
512 The DN specifier behaves much like <what> clause DN specifiers.
[all …]
H A Dslapdconfig.sdf315 DN.
333 H4: rootdn <DN>
335 This directive specifies the DN that is not subject to
337 operations on this database. The DN need not refer to
339 DN may refer to a SASL identity.
383 Queries with a DN ending in "dc=example,dc=com"
396 > searchbase=<base DN>
411 > [binddn=<DN>]
428 > [suffixmassage=<real DN>]
429 > [logbase=<base DN>]
[all …]
H A Dtls.sdf27 The {{TERM:DN}} of a server certificate must use the {{EX:CN}}
36 The DN of a client certificate can be used directly as an
37 authentication DN.
39 is also based on X.500, both use the same DN formats and
40 generally the DN in a user's X.509 certificate should be
41 identical to the DN of their LDAP entry. However, sometimes
/netbsd/external/bsd/openldap/dist/servers/slapd/back-ldap/
H A DTODO.proxy16 It could do some rewriting to map everything that comes in with a base DN
18 everything that comes in with a base DN of "o=Branch 2, dc=company, dc=net"
20 base. Everything that comes in with a base DN of "dc=company, dc=net" should
38 exact DN exact parent ancestor
50 The backend must rely on a DN fetching mechanism. Each operation requires
61 Two layers of depth in DN fetching are envisaged.
63 retrieved entries. The cache relates each RDN (i.e. the DN apart from the
77 Again, the lag between the fetching of the required DN and the actual
84 cache-level DN fetch.
93 by performing a cache DN fetch of the base first.
[all …]
/netbsd/crypto/external/bsd/heimdal/dist/lib/hx509/data/
H A Dnist-data2148 # 4.13.1 Valid DN nameConstraints Test1 - Validate Successfully
150 # 4.13.2 Invalid DN nameConstraints Test2 - Reject - name constraints violation
152 # 4.13.3 Invalid DN nameConstraints Test3 - Reject - name constraints violation
154 # 4.13.4 Valid DN nameConstraints Test4 - Validate Successfully
156 # 4.13.5 Valid DN nameConstraints Test5 - Validate Successfully
158 # 4.13.6 Valid DN nameConstraints Test6 - Validate Successfully
168 # 4.13.11 Valid DN nameConstraints Test11 - Validate Successfully
174 # 4.13.14 Valid DN nameConstraints Test14 - Validate Successfully
182 # 4.13.18 Valid DN nameConstraints Test18 - Validate Successfully
184 # 4.13.19 Valid Self-Issued DN nameConstraints Test19 - Validate Successfully
[all …]
/netbsd/external/bsd/openldap/dist/doc/rfc/
H A Drfc4514.txt71 representation to a string. Section 3 details how to convert a DN
357 Implementations MAY recognize other DN string representations.
358 However, as there is no requirement that alternative DN string
632 DN strings. Issues with presentation of translated DN strings are
636 This appendix provides guidance for applications presenting DN
650 When a DN string is displayed in free-form text, it is often
661 are not part of the DN string.
669 DN string is long:
683 to be removed before the DN string is used in LDAP.
686 the user which whitespace is part of the DN string and which
[all …]
H A Drfc3296.txt100 Distinguished Name (DN) [RFC2253].
152 contain a non-empty DN. The handling of LDAP URLs with absent or
153 empty DN parts or with explicit scope specifier is not defined by
182 component of an entry's DN [RFC2253].
242 Typically the DN of the referral object and the DN of the object in
321 modify, and modify DN operations. If the client requests any of
327 DN to be returned is the same as the target DN, the DN part SHOULD
400 has a DN of "CN=Manager,OU=Roles,O=MNN,C=WW", the server will
423 object, the DN part of the URI MUST be replaced with the base DN as
523 returned as is. If the LDAP URL's DN part is absent or empty, the DN
[all …]
H A Drfc2377.txt217 distinguished name (DN) would then be
274 different attributes but the same DN) in different (e.g.
343 construct the DN
433 The domain component attributes of a user's DN will normally be
440 The full LDAP DN for this user would then be:
511 To provide an example of a DN which deviates from what might be
526 The DN of J.Smith in this case will be:
532 components of the DN. For instance, the DN for a J.Smith could be:
539 significant pieces of the DN and the uid are the same (i.e.,
578 servers) with a DN, the LDAP URL provides unified high-level
[all …]
H A Drfc5020.txt67 is identified by its distinguished name (DN) [RFC4512]. However, as
68 an entry's DN is not an attribute of the entry, it is not possible to
98 current DN.
104 DESC 'DN of the entry'
119 Note that the DN of the entry cannot be modified through this
125 entry's DN, the introduction of this attribute is not believed to
H A Drfc3088.txt85 2.1. DN to Domain Name Mapping
87 The service maps a DN [RFC2253] to a fully qualified domain name
151 the root of the domain tree to a DN. We suggest the root of the
155 DN "DC=example,DC=net", not to "DC=example,DC=net,DC=.". As it is
156 not our intent to introduce or support an alternative domain to DN
161 DN "DC=example,DC=net", not to "DC=example,DC=.,DC=net". As it is
162 not our intent to introduce or support an alternative domain to DN
178 be coded to return invalid DN error.
234 return a referral result if the target (or base) DN can be mapped to
275 If DNS location information is available for the base DN itself, the
/netbsd/external/bsd/openldap/dist/doc/drafts/
H A Ddraft-ietf-ldapext-locate-xx.txt73 Name (DN) [2] on which the operation is performed. A client, or a
75 server(s) that hold the naming context containing that DN, since
122 This section defines a method of converting a DN into a DNS domain
128 The output domain name is initially empty. The DN is processed in
138 processing stops, the DN cannot be converted into a domain name.
140 For DN:
166 domain name formed by converting the DN of a naming context mastered
180 server for a particular DN converts that DN to a domain name using
185 for the DN "ou=foo,dc=example,dc=net" that supports the TCP protocol
198 matching SRV records available for the converted DN the client SHOULD
[all …]
/netbsd/external/bsd/openldap/dist/contrib/slapd-modules/variant/tests/data/
H A Dtest011-out.ldif5 Matched DN: cn=Gern Jensen,ou=Information Technology Division,ou=People,dc=example,dc=com
9 Matched DN: cn=Gern Jensen,ou=Information Technology Division,ou=People,dc=example,dc=com
/netbsd/external/bsd/openldap/dist/contrib/slapd-modules/nssov/
H A DREADME83 inherently secure. Two methods of mapping the PAM username to an LDAP DN
86 this case, a DN of the form
88 is fed into the regexp matcher. If a match is produced, the resulting DN
93 If no DN is found, the overlay returns PAM_USER_UNKNOWN. If the DN is
/netbsd/crypto/external/bsd/openssl/dist/doc/internal/man3/
H A Dossl_cmp_hdr_init.pod65 is the NULL-DN.
72 If B<nm> is NULL, recipient is set to the NULL DN (the empty list of strings).
113 to the client it set to the NULL-DN. In this case for identification at least
128 ossl_cmp_general_name_is_NULL_DN() returns 1 given a NULL-DN, else 0.
/netbsd/crypto/external/bsd/openssl.old/dist/doc/man3/
H A DX509_check_host.pod86 to consider the subject DN even if the certificate contains at least
88 address as appropriate); the default is to ignore the subject DN
92 consider the subject DN even if the certificate contains no subject alternative
94 is to use the subject DN when no corresponding subject alternative names are
98 precedence and the subject DN is not checked for matching names.
/netbsd/crypto/external/bsd/openssl/dist/doc/man3/
H A DX509_check_host.pod91 to consider the subject DN even if the certificate contains at least
93 address as appropriate); the default is to ignore the subject DN
97 consider the subject DN even if the certificate contains no subject alternative
99 is to use the subject DN when no corresponding subject alternative names are
103 precedence and the subject DN is not checked for matching names.
/netbsd/external/bsd/openldap/dist/servers/slapd/back-relay/
H A DREADME6 The DN rewrite, filter rewrite and attributeType/objectClass
21 database selection and DN rewriting.
71 # old fashioned suffixalias, applied also to DN-valued attributes
/netbsd/external/bsd/openldap/dist/servers/slapd/schema/
H A Dcosine.ldif57 4: DN of manager' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115
69 'RFC1274: DN of author of document' EQUALITY distinguishedNameMatch SYNTAX 1
79 1274: DN of secretary' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.146
96 'RFC1274: DN of entry associated with domain' EQUALITY distinguishedNameMatc
/netbsd/external/gpl3/gdb/dist/gas/testsuite/gas/metag/
H A Dmetadsp21-invalid.s6 DN MUL D0Re0, D0Re0, [D0AR.0+D0ARI.1++] label
/netbsd/external/gpl3/gdb.old/dist/gas/testsuite/gas/metag/
H A Dmetadsp21-invalid.s6 DN MUL D0Re0, D0Re0, [D0AR.0+D0ARI.1++] label

12345678