1sasl_client_step(10 July 2001)                  sasl_client_step(10 July 2001)
2
3
4

NAME

6       sasl_client_step - Perform a step in the authentication negotiation
7
8
9

SYNOPSIS

11       #include <sasl/sasl.h>
12
13       int sasl_client_step(sasl_conn_t *conn,
14                      const char *serverin,
15                      unsigned serverinlen,
16                      sasl_interact_t ** prompt_need,
17                      const char ** clientout,
18                      unsigned * clientoutlen);
19
20

DESCRIPTION

22       sasl_client_step()  performs  a step in the authentication negotiation.
23       It returns SASL_OK if the whole negotiation is successful and SASL_CON‐
24       TINUE if this step is ok but at least one more step is needed. A client
25       should not assume an  authentication  negotiation  is  successful  just
26       because  the  server  signaled success via protocol (i.e. if the server
27       said ". OK Authentication succeeded" in  IMAP  sasl_client_step  should
28       still be called one more time with a serverinlen of zero.
29
30       If SASL_INTERACT is returned the library needs some values to be filled
31       in before it can proceed. The prompt_need structure will be  filled  in
32       with  requests.  The application should fulfill these requests and call
33       sasl_client_start again  with  identical  parameters  (the  prompt_need
34       parameter  will  be  the  same  pointer  as before but filled in by the
35       application).
36
37       conn is the SASL connection context
38
39       serverin is the data given by  the  server  (decoded  if  the  protocol
40       encodes requests sent over the wire)
41
42       serverinlen is the length of serverin
43
44       clientout  and  clientoutlen  is  created.  It  is  the  initial client
45       response to send to the server. It is the job of the client to send  it
46       over  the  network to the server.  Any protocol specific encoding (such
47       as base64 encoding) necessary needs to be done by the client.
48
49

RETURN VALUE

51       sasl_client_step returns an integer which corresponds  to  one  of  the
52       following  codes.  SASL_CONTINUE  indicates  success and that there are
53       more steps needed in the authentication.  SASL_OK  indicates  that  the
54       authentication  is complete. All other return codes indicate errors and
55       should either be handled or the authentication session should be quit.
56
57

CONFORMING TO

59       RFC 2222
60

SEE ALSO

62       sasl(3),   sasl_callbacks(3),   sasl_errors(3),    sasl_client_init(3),
63       sasl_client_new(3), sasl_client_start(3)
64
65
66
67SASL man pages                       SASL       sasl_client_step(10 July 2001)
Impressum