| /netbsd-src/external/bsd/openldap/dist/tests/scripts/ |
| H A D | test026-dn | 68 DN="OU=Sales+CN=J. Smith,DC=example,DC=net"
69 echo "Searching database for DN=\"$DN\"..."
70 echo "# Searching database for DN=\"$DN\"..." >> $SEARCHOUT
72 "(member=$DN)" >> $SEARCHOUT 2>&1
81 DN="testUUID=597ae2f6-16a6-1027-98f4-ABCDEFabcdef,DC=Example"
82 echo "Searching database for entryUUID-named DN=\"$DN\"..."
83 echo "# Searching database for entryUUID-named DN=\"$DN\"..." >> $SEARCHOUT
85 "(member=$DN)" \
95 DN="dc=example,dc=com"
96 echo "Searching database for nameAndOptionalUID=\"$DN\"..."
[all …]
|
| H A D | test032-chain | 156 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-src/external/bsd/openldap/dist/tests/data/ |
| H A D | dn.out | 11 description: RFC 1779 compliant DN string representation
16 description: RFC 2253 compliant DN string representation
58 description: "member" values contain specific DN forms;
59 description: "seeAlso" values contain DN forms already defined as "member",
62 description: "seeAlso" DN string representations used above.
85 only DN portion
86 description: #'1'B // empty "" DN
87 description: #'0010'B // empty "" DN with leading '0's
88 description: dc=example,dc=com#'1000'B // with DN portion
89 description: dc=example,dc=com#''B // with DN portion + bitstring with no bits
[all …]
|
| H A D | test-dn.ldif | 11 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
28 # DN forms already defined as "member" in a different string representation
33 description: "member" values contain specific DN forms;
34 description: "seeAlso" values contain DN forms already defined as "member",
37 description: "seeAlso" DN string representations used above.
178 description: RFC 1779 compliant DN string representation
216 # Other DN-related syntaxes
230 description: cn=Name and Optional UID,ou=Related Syntaxes,dc=example,dc=com // only DN portion
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/guide/admin/ |
| H A D | sasl.sdf | 96 mapping authentication identities to LDAP {{TERM:DN}}'s, which
139 associates an authentication request DN of the form:
147 {{EX:kurt@EXAMPLE.COM}} would have the associated DN:
152 associated DN:
157 The authentication request DN can be used directly in ACLs and
159 LDAP DN format. Or alternatively, the authentication DN could be
164 an extra component in the authorization DN, regardless of any
214 DN}} of the form
219 authentication request DN would be:
223 This authentication request DN can be used directly ACLs or,
[all …]
|
| H A D | access-control.sdf | 41 > [dn[.<basic-style>]=<regex> | dn.<scope-style>=<DN>]
48 > | dn[.<basic-style>]=<regex> | dn.<scope-style>=<DN>]
76 commonly selected in two ways: by DN and by filter. The following
77 qualifiers select entries by DN:
81 > to dn.<scope-style>=<DN>
85 the target entry's {{normalized DN}}. (The second form is not
87 select entries which are within the requested scope of DN. The
88 <DN> is a string representation of the Distinguished Name, as
93 provided DN, {{EX:one}} matches the entries whose parent is the
94 provided DN, {{EX:subtree}} matches all entries in the subtree whose
[all …]
|
| H A D | slapdconfig.sdf | 315 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.
355 This directive can be used to specifies a password for the DN for
356 the rootdn (when the rootdn is set to a DN within the database).
374 This directive specifies the DN suffix of queries that will be
383 Queries with a DN ending in "dc=example,dc=com"
396 > searchbase=<base DN>
[all …]
|
| H A D | tls.sdf | 27 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-src/external/bsd/openldap/dist/servers/slapd/back-ldap/ |
| H A D | TODO.proxy | 16 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-src/crypto/external/bsd/heimdal/dist/lib/hx509/data/ |
| H A D | nist-data2 | 148 # 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
160 # 4.13.7 Invalid DN nameConstraints Test7 - Reject - name constraints violation
162 # 4.13.8 Invalid DN nameConstraints Test8 - Reject - name constraints violation
164 # 4.13.9 Invalid DN nameConstraints Test9 - Reject - name constraints violation
166 # 4.13.10 Invalid DN nameConstraints Test10 - Reject - name constraints violation
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/doc/rfc/ |
| H A D | rfc4514.txt | 45 The structure of a DN [X.501] is described in terms of ASN.1 [X.680].
70 RECOMMENDED algorithm for converting a DN from its ASN.1 structured
71 representation to a string. Section 3 details how to convert a DN
74 While other documents may define other algorithms for converting a DN
357 Implementations MAY recognize other DN string representations.
358 However, as there is no requirement that alternative DN string
360 SHOULD only generate DN strings in accordance with Section 2 of this
630 may be desirable to present non-translated DN strings to users. This
632 DN strings. Issues with presentation of translated DN strings are
636 This appendix provides guidance for applications presenting DN
[all …]
|
| H A D | rfc3296.txt | 100 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
325 The DN part MUST be modified such that it refers to the appropriate
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
407 Note that the DN part of the LDAP URL is modified such that it
[all …]
|
| H A D | rfc2377.txt | 217 distinguished name (DN) would then be
274 different attributes but the same DN) in different (e.g.
312 information encoded in his/her own DN. Names that are totally opaque
318 behind the terms distinguished name (DN) and relative distinguished
328 [3][10]. It is used in the construction of a DN from a domain name.
343 construct the DN
347 from its domain name. It would then use this DN as the root of its
350 The DN itself can be used to identify a directory organization object
354 The subordinates of the DN will be directory objects related to the
418 his/her DN, there is some hope that it will be recognizable when such
[all …]
|
| H A D | rfc5020.txt | 67 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 D | rfc3088.txt | 85 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-src/external/bsd/openldap/dist/doc/drafts/ |
| H A D | draft-ietf-ldapext-locate-xx.txt | 73 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 …]
|
| H A D | draft-sermersheim-ldap-distproc-xx.txt | 162 distinguished name (DN). Operation evaluation is the act of
397 DN of the operation being progressed. This field must be allowed
423 populated with an empty DN.
473 subtree of entries below the base DN, but does not include the base
474 DN itself. This is used here when progressing distributed search
585 This field contains the new target (or base) DN for the operation.
589 the case where an alias has been dereferenced while resolving the DN,
601 than the base DN held in the ChainedRequestValue.operationRequest.
613 DN to name the immediate superior of a context prefix.
620 DSA and DN that has already been contacted while attempting to
[all …]
|
| /netbsd-src/external/bsd/openldap/dist/contrib/slapd-modules/variant/tests/data/ |
| H A D | test011-out.ldif | 5 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-src/external/bsd/openldap/dist/contrib/slapd-modules/nssov/ |
| H A D | README | 83 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-src/crypto/external/bsd/openssl/dist/doc/internal/man3/ |
| H A D | ossl_cmp_hdr_init.pod | 65 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-src/crypto/external/bsd/openssl.old/dist/doc/man3/ |
| H A D | X509_check_host.pod | 86 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-src/crypto/external/bsd/openssl/dist/doc/man3/ |
| H A D | X509_check_host.pod | 91 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.
|
| H A D | X509V3_set_ctx.pod | 26 contained in a subject DN, the subject DN is taken from I<subject> or I<req>.
|
| /netbsd-src/external/bsd/openldap/dist/servers/slapd/back-relay/ |
| H A D | README | 6 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-src/external/bsd/openldap/dist/servers/slapd/schema/ |
| H A D | cosine.ldif | 57 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
|