1 .TH LDAP_BIND 3 "2008/07/16" "OpenLDAP 2.4.11"
2 .\" $OpenLDAP: pkg/ldap/doc/man/man3/ldap_bind.3,v 1.20.2.5 2008/02/11 23:26:39 kurt Exp $
3 .\" Copyright 1998-2008 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 ldap_bind, ldap_bind_s, ldap_simple_bind, ldap_simple_bind_s, ldap_sasl_bind, ldap_sasl_bind_s, ldap_sasl_interactive_bind_s, ldap_parse_sasl_bind_result, ldap_unbind, ldap_unbind_s, ldap_unbind_ext, ldap_unbind_ext_s, ldap_set_rebind_proc \- LDAP bind routines
8 OpenLDAP LDAP (libldap, -lldap)
13 .BI "int ldap_bind(LDAP *" ld ", const char *" who ", const char *" cred ","
15 .BI "int " method ");"
18 .BI "int ldap_bind_s(LDAP *" ld ", const char *" who ", const char *" cred ","
20 .BI "int " method ");"
23 .BI "int ldap_simple_bind(LDAP *" ld ", const char *" who ", const char *" passwd ");"
25 .BI "int ldap_simple_bind_s(LDAP *" ld ", const char *" who ", const char *" passwd ");"
27 .BI "int ldap_sasl_bind(LDAP *" ld ", const char *" dn ", const char *" mechanism ","
29 .BI "struct berval *" cred ", LDAPControl *" sctrls "[],"
30 .BI "LDAPControl *" cctrls "[], int *" msgidp ");"
33 .BI "int ldap_sasl_bind_s(LDAP *" ld ", const char *" dn ", const char *" mechanism ","
35 .BI "struct berval *" cred ", LDAPControl *" sctrls "[],"
36 .BI "LDAPControl *" cctrls "[], struct berval **" servercredp ");"
39 .BI "int ldap_parse_sasl_bind_result(LDAP *" ld ", LDAPMessage *" res ","
41 .BI "struct berval **" servercredp ", int " freeit ");"
44 .BI "int ldap_sasl_interactive_bind_s(LDAP *" ld ", const char *" dn ","
46 .BI "const char *" mechs ","
47 .BI "LDAPControl *" sctrls "[], LDAPControl *" cctrls "[],"
48 .BI "unsigned " flags ", LDAP_SASL_INTERACT_PROC *" interact ","
49 .BI "void *" defaults ");"
52 .BI "int (LDAP_SASL_INTERACT_PROC)(LDAP *" ld ", unsigned " flags ", void *" defaults ", void *" sasl_interact ");"
54 .BI "int ldap_unbind(LDAP *" ld ");"
56 .BI "int ldap_unbind_s(LDAP *" ld ");"
58 .BI "int ldap_unbind_ext(LDAP *" ld ", LDAPControl *" sctrls "[],"
60 .BI "LDAPControl *" cctrls "[]);"
63 .BI "int ldap_unbind_ext_s(LDAP *" ld ", LDAPControl *" sctrls "[],"
65 .BI "LDAPControl *" cctrls "[]);"
68 .BI "int ldap_set_rebind_proc (LDAP *" ld ", LDAP_REBIND_PROC *" ldap_proc ", void *" params ");"
70 .BI "int (LDAP_REBIND_PROC)(LDAP *" ld ", LDAP_CONST char *" url ", ber_tag_t " request ", ber_int_t " msgid ", void *" params ");"
73 These routines provide various interfaces to the LDAP bind operation.
74 After an association with an LDAP server is made using
76 an LDAP bind operation should be performed before other operations are
77 attempted over the connection. An LDAP bind is required when using
78 Version 2 of the LDAP protocol; it is optional for Version 3 but is
79 usually needed due to security considerations.
81 There are three types of bind calls, ones providing simple authentication,
82 ones providing SASL authentication, and general routines capable of doing
83 either simple or SASL authentication.
86 (Simple Authentication and Security Layer)
87 that can negotiate one of many different kinds of authentication.
88 Both synchronous and asynchronous versions of each variant of the bind
89 call are provided. All routines
90 take \fIld\fP as their first parameter, as returned from
92 .SH SIMPLE AUTHENTICATION
93 The simplest form of the bind call is
94 .BR ldap_simple_bind_s() .
95 It takes the DN to bind as in \fIwho\fP, and the userPassword associated
96 with the entry in \fIpasswd\fP. It returns an LDAP error indication
100 .B ldap_simple_bind()
101 call is asynchronous,
102 taking the same parameters but only initiating the bind operation and
103 returning the message id of the request it sent. The result of the
104 operation can be obtained by a subsequent call to
106 .SH GENERAL AUTHENTICATION
111 routines can be used when the
112 authentication method to use needs to be selected at runtime. They
113 both take an extra \fImethod\fP parameter selecting the authentication
114 method to use. It should be set to LDAP_AUTH_SIMPLE
115 to select simple authentication.
117 returns the message id of the request it initiates.
119 returns an LDAP error indication.
120 .SH SASL AUTHENTICATION
121 For SASL binds the server always ignores any provided DN, so the
123 parameter should always be NULL.
124 .BR ldap_sasl_bind_s ()
125 sends a single SASL bind request with the given SASL
127 and credentials in the
129 parameter. The format of the credentials depends on the particular
130 SASL mechanism in use. For mechanisms that provide mutual authentication
131 the server's credentials will be returned in the
134 The routine returns an LDAP error indication (see
137 .BR ldap_sasl_bind ()
138 call is asynchronous, taking the same parameters but only sending the
139 request and returning the message id of the request it sent. The result of
140 the operation can be obtained by a subsequent
143 The result must be additionally parsed by
144 .BR ldap_parse_sasl_bind_result ()
145 to obtain any server credentials sent from the server.
147 Many SASL mechanisms require multiple message exchanges to perform a
148 complete authentication. Applications should generally use
149 .BR ldap_sasl_interactive_bind_s ()
150 rather than calling the basic
151 .BR ldap_sasl_bind ()
152 functions directly. The
154 parameter should contain a space-separated list of candidate mechanisms
155 to use. If this parameter is NULL or empty the library will query
156 the supportedSASLMechanisms attribute from the server's rootDSE
157 for the list of SASL mechanisms the server supports. The
159 parameter controls the interaction used to retrieve any necessary
160 SASL authentication parameters and should be one of:
163 use defaults if available, prompt otherwise
165 LDAP_SASL_INTERACTIVE
173 function uses the provided
175 to handle requests from the SASL library for particular authentication
176 parameters. There is no defined format for the
179 it is up to the caller to use whatever format is appropriate for the
185 parameter comes from the underlying SASL library. When used with Cyrus SASL
188 structures. The Cyrus SASL library will prompt for a variety of inputs,
192 the realm for the authentication attempt
195 the username to authenticate
198 the password for the provided username
201 the username to use for proxy authorization
204 generic prompt for input with input echoing disabled
207 generic prompt for input with input echoing enabled
210 indicates the end of the array of prompts
212 See the Cyrus SASL documentation for more details.
216 .B ldap_set_rebind_proc
217 function() sets the process to use for binding when an operation returns a
218 referral. This function is used when an application needs to bind to another server
219 in order to follow a referral or search continuation reference.
221 The function takes \fIld\fP, the \fIrebind\fP function, and the \fIparams\fP,
222 the arbitrary data like state information which the client might need to properly rebind.
223 The LDAP_OPT_REFERRALS option in the \fIld\fP must be set to ON for the libraries
224 to use the rebind function. Use the
226 function to set the value.
228 The rebind function parameters are as follows:
230 The \fIld\fP parameter must be used by the application when binding to the
231 referred server if the application wants the libraries to follow the referral.
233 The \fIurl\fP parameter points to the URL referral string received from the LDAP server.
234 The LDAP application can use the
235 .BR ldap_url_parse (3)
236 function to parse the string into its components.
238 The \fIrequest\fP parameter specifies the type of request that generated the referral.
240 The \fImsgid\fP parameter specifies the message ID of the request generating the referral.
242 The \fIparams\fP parameter is the same value as passed originally to the
243 .BR ldap_set_rebind_proc ()
246 The LDAP libraries set all the parameters when they call the rebind function. The application
247 should not attempt to free either the ld or the url structures in the rebind function.
249 The application must supply to the rebind function the required authentication information such as,
250 user name, password, and certificates. The rebind function must use a synchronous bind method.
254 call is used to unbind from the directory,
255 terminate the current association, and free the resources contained
256 in the \fIld\fP structure. Once it is called, the connection to
257 the LDAP server is closed, and the \fIld\fP structure is invalid.
260 call is just another name for
262 both of these calls are synchronous in nature.
267 .B ldap_unbind_ext_s()
268 allows the operations to specify controls.
270 Asynchronous routines will return -1 in case of error, setting the
271 \fIld_errno\fP parameter of the \fIld\fP structure. Synchronous
272 routines return whatever \fIld_errno\fP is set to. See
274 for more information.
276 If an anonymous bind is sufficient for the application, the rebind process
277 need not be provided. The LDAP libraries with the LDAP_OPT_REFERRALS option
278 set to ON (default value) will automatically follow referrals using an anonymous bind.
280 If the application needs stronger authentication than an anonymous bind,
281 you need to provide a rebind process for that authentication method.
282 The bind method must be synchronous.
287 .BR ldap_set_option (3),
288 .BR ldap_url_parse (3)
290 (http://www.rfc-editor.org),
292 (http://asg.web.cmu.edu/sasl/)
294 .\" Shared Project Acknowledgement Text
295 .B "OpenLDAP Software"
296 is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>.
297 .B "OpenLDAP Software"
298 is derived from University of Michigan LDAP 3.3 Release.