2 .\" Copyright (C) 1998-2003, Carnegie Mellon Univeristy. All Rights Reserved.
3 .\" Portions Copyright (C) 2003, Sun Microsystems,
4 .\" Inc. All Rights Reserved
5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
6 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
7 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
8 .TH SASL_CLIENT_START 3SASL "May 13, 2017"
10 sasl_client_start \- perform a step in the authentication negotiation
14 \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lsasl\fR [ \fIlibrary\fR ... ]
15 #include <sasl/sasl.h>
17 \fBint\fR \fBsasl_client_start\fR(\fBsasl_conn_t *\fR\fIconn\fR, \fBconst char *\fR\fImechlist\fR,
18 \fBsasl_interact_t **\fR\fIprompt_need\fR, \fBconst char **\fR\fIclientout\fR,
19 \fBunsigned *\fR\fIclientoutlen\fR, \fBconst char **\fR\fImech\fR);
24 Use the \fBsasl_client_start()\fR interface to select a mechanism for
25 authentication and start the authentication session. The \fImechlist\fR
26 parameter holds the list of mechanisms that the client might like to use. The
27 mechanisms in the list are not necessarily supported by the client, nor are the
28 mechanisms necessarily valid. SASL determines which of the mechanisms to use
29 based upon the security preferences specified earlier. The list of mechanisms
30 is typically a list of mechanisms that the server supports, acquired from a
34 If \fBSASL_INTERACT\fR is returned, the library needs some values to be filled
35 in before it can proceed. The \fIprompt_need\fR structure is filled in with
36 requests. The application fullfills these requests and calls
37 \fBsasl_client_start()\fR again with identical parameters. The
38 \fIprompt_need\fR parameter is the same pointer as before, but it is filled in
46 The SASL connection context.
55 A list of mechanism that the server has available. Punctuation is ignored.
61 \fB\fIprompt_need\fR\fR
64 A list of prompts that are needed to continue, if necessary.
74 \fB\fIclientoutlen\fR\fR
77 \fIclientout\fR and \fIclientoutlen\fR are created. They contain the initial
78 client response to send to the server. It is the job of the client to send them
79 over the network to the server. Any protocol specific encodingthat is
80 necessary, for example \fBbase64\fR encoding, must be done by the client.
82 If the protocol lacks client-send-first capability, then set \fIclientout\fR to
83 \fINULL\fR. If there is no initial client-send, then *\fIclientout\fR will be
84 set to \fINULL\fR on return.
93 Contains the name of the chosen SASL mechanism, upon success.
98 \fBsasl_client_start()\fR returns an integer that corresponds to a SASL error
103 \fB\fBSASL_CONTINUE\fR\fR
106 The call to \fBsasl_client_start()\fR was successful, and more steps are needed
107 in the authentication.
112 All other error codes indicate an error situation that must be handled, or the
113 authentication session should be quit. See \fBsasl_errors\fR(3SASL) for
114 information on SASL error codes.
117 See \fBattributes\fR(5) for descriptions of the following attributes:
125 ATTRIBUTE TYPE ATTRIBUTE VALUE
127 Interface Stability Evolving
134 \fBsasl_errors\fR(3SASL), \fBattributes\fR(5)