Seth Woolley's Man Viewer

sasl_client_step(3) - sasl_client_step - Perform a step in the authentication negotiation - man 3 sasl_client_step

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

sasl_client_step(10 July 2001)                  sasl_client_step(10 July 2001)

       sasl_client_step - Perform a step in(1,8) the authentication negotiation

       #include <sasl/sasl.h>

       int sasl_client_step(sasl_conn_t *conn,
                      const char *serverin,
                      unsigned serverinlen,
                      sasl_interact_t ** prompt_need,
                      const char ** clientout,
                      unsigned * clientoutlen);

       sasl_client_step()  performs  a step in(1,8) the authentication negotiation.
       It returns SASL_OK if(3,n) the whole negotiation is successful and SASL_CON-
       TINUE if(3,n) this step is ok but at least one more step is needed. A client
       should not assume an  authentication  negotiation  is  successful  just
       because  the  server  signaled success via protocol (i.e. if(3,n) the server
       said ". OK Authentication succeeded" in(1,8)  IMAP  sasl_client_step  should
       still be called one more time(1,2,n) with a serverinlen of zero.

       If SASL_INTERACT is returned the library needs some values to be filled
       in(1,8) before it can proceed. The prompt_need structure will be  filled  in(1,8)
       with  requests.  The application should fulfill these requests and call
       sasl_client_start again  with  identical  parameters  (the  prompt_need
       parameter  will  be  the  same  pointer  as before but filled in(1,8) by the

       conn is the SASL connection context

       serverin is the data given by  the  server  (decoded  if(3,n)  the  protocol
       encodes requests sent over the wire)

       serverinlen is the length of serverin

       clientout  and  clientoutlen  is  created.  It  is  the  initial client
       response to send(2,n) to the server. It is the job of the client to send(2,n)  it
       over  the  network to the server.  Any protocol specific encoding(3,n) (such
       as base64 encoding(3,n)) necessary needs to be done by the client.

       sasl_client_step returns an integer which corresponds  to  one  of  the
       following  codes.  SASL_CONTINUE  indicates  success and that there are
       more steps needed in(1,8) the authentication.  SASL_OK  indicates  that  the
       authentication  is complete. All other return codes indicate errors and
       should either be handled or the authentication session should be  quit.

       RFC 2222

       sasl(3),    sasl_callbacks(3),   sasl_errors(3),   sasl_client_init(3),
       sasl_client_new(3), sasl_client_start(3)

SASL man(1,5,7) pages                       SASL       sasl_client_step(10 July 2001)

References for this manual (incoming links)