openldap/doc/man/man3/ldap_get_dn.3

104 lines
3.2 KiB
Groff
Raw Normal View History

2001-07-23 12:16:42 +08:00
.TH LDAP_GET_DN 3 "22 July 2001" "OpenLDAP LDVERSION"
1999-09-12 12:41:47 +08:00
.\" $OpenLDAP$
2000-05-13 10:47:56 +08:00
.\" Copyright 1998-2000 The OpenLDAP Foundation All Rights Reserved.
1999-09-12 12:41:47 +08:00
.\" Copying restrictions apply. See COPYRIGHT/LICENSE.
1998-08-09 08:43:13 +08:00
.SH NAME
2001-06-12 04:45:06 +08:00
ldap_get_dn, ldap_explode_dn, ldap_explode_rdn, ldap_dn2ufn \- LDAP DN handling routines
1998-08-09 08:43:13 +08:00
.SH SYNOPSIS
.nf
.ft B
#include <ldap.h>
.LP
.ft B
2001-07-23 12:12:58 +08:00
char *ldap_get_dn( LDAP *ld, LDAPMessage *entry )
1998-08-09 08:43:13 +08:00
.LP
.ft B
2001-07-23 12:12:58 +08:00
char **ldap_explode_dn( const char *dn, int notypes )
1998-08-09 08:43:13 +08:00
.LP
.ft B
2001-07-23 12:12:58 +08:00
char **ldap_explode_rdn( const char *rdn, int notypes )
2001-06-12 04:45:06 +08:00
.LP
.ft B
2001-07-23 12:12:58 +08:00
char *ldap_dn2ufn( const char * dn )
1998-08-09 08:43:13 +08:00
.SH DESCRIPTION
These routines allow LDAP entry names (Distinguished Names, or DNs)
to be obtained, parsed, converted to a user-friendly form, and tested.
2000-09-02 06:10:19 +08:00
A DN has the form described in
RFC 2253 "Lightweight Directory Access Protocol (v3):
UTF-8 String Representation of Distinguished Names".
1998-08-09 08:43:13 +08:00
.LP
The
.B ldap_get_dn()
routine takes an \fIentry\fP as returned by
.BR ldap_first_entry (3)
or
.BR ldap_next_entry (3)
and returns a copy of
the entry's DN. Space for the DN will be obtained dynamically
and should be freed by the caller using
.BR ldap_memfree (3).
1998-08-09 08:43:13 +08:00
.LP
The
.B ldap_explode_dn()
routine takes a DN as returned by
.B ldap_get_dn()
and breaks it up into its component parts. Each part is known as a
Relative Distinguished Name, or RDN.
.B ldap_explode_dn()
returns a
NULL-terminated array, each component of which contains an RDN from the
DN. The \fInotypes\fP parameter is used to request that only the RDN
values be returned, not their types. For example, the DN "cn=Bob,
c=US" would return as either { "cn=Bob", "c=US", NULL } or { "Bob",
"US", NULL }, depending on whether notypes was 0 or 1, respectively.
The result can be freed by calling
.BR ldap_value_free (3).
.LP
1998-11-05 07:28:51 +08:00
Similarly, the
.B ldap_explode_rdn()
routine takes an RDN as returned by
.B ldap_explode_dn(dn,0)
and breaks it up into its "type=value" component parts (or just "value",
2001-07-23 12:12:58 +08:00
if the \fInotypes\fP parameter is set). Note the value is not
unescaped. The result can be freed by calling
1998-11-05 07:28:51 +08:00
.BR ldap_value_free (3).
2001-06-12 04:45:06 +08:00
.LP
.B ldap_dn2ufn()
is used to turn a DN as returned by
2001-07-23 12:12:58 +08:00
.BR ldap_get_dn (3)
into a more user-friendly form, stripping off all type names. See
"Using the Directory to Achieve User Friendly Naming" (RFC 1781)
for more details on the UFN format. Due to the ambigious nature
of the format, it is generally only used for display purposes.
The space for the UFN returned is obtained dynamically and the user
is responsible for freeing it via a call to
2001-06-12 04:45:06 +08:00
.BR ldap_memfree (3).
1998-08-09 08:43:13 +08:00
.SH ERRORS
If an error occurs in
.BR ldap_get_dn() ,
NULL is returned and the
.B ld_errno
field in the \fIld\fP parameter is set to indicate the error. See
.BR ldap_error (3)
for a description of possible error codes.
2001-06-12 04:45:06 +08:00
.BR ldap_explode_dn() ,
.BR ldap_explode_rdn() ,
and
.B ldap_dn2ufn()
1998-08-09 08:43:13 +08:00
will return NULL with
.BR errno (3)
set appropriately in case of trouble.
.SH NOTES
2001-07-29 19:46:41 +08:00
These routines dynamically allocate memory that the caller must free.
1998-08-09 08:43:13 +08:00
.SH SEE ALSO
.BR ldap(3),
.BR ldap_error(3),
.BR ldap_first_entry(3),
.BR ldap_memfree(3),
1998-08-09 08:43:13 +08:00
.BR ldap_value_free(3)
1998-10-25 09:41:42 +08:00
.SH ACKNOWLEDGEMENTS
.B OpenLDAP
is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
.B OpenLDAP
is derived from University of Michigan LDAP 3.3 Release.