Seth Woolley's Man Viewer

ldap_parse_sasl_bind_result(3) - ldap_parse_result - Parsing results - man 3 ldap_parse_sasl_bind_result

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

LDAP_PARSE_RESULT(3)                                      LDAP_PARSE_RESULT(3)



NAME
       ldap_parse_result - Parsing results

LIBRARY
       OpenLDAP LDAP (libldap, -lldap)

SYNOPSIS
       #include <ldap.h>

       int ldap_parse_result( LDAP *ld(1,8), LDAPMessage *result,
            int *errcodep, char **matcheddnp, char **errmsgp,
            char ***referralsp, LDAPControl ***serverctrlsp,
            int freeit )

       int ldap_parse_sasl_bind_result( LDAP *ld(1,8), LDAPMessage *result,
            struct berval **servercredp, int freeit )

       int ldap_parse_extended_result( LDAP *ld(1,8), LDAPMessage *result,
            char **retoidp, struct berval **retdatap, int freeit )

DESCRIPTION
       These  routines  are used to extract information from a result message.
       They will operate on the first result message  in(1,8)  a  chain  of  search
       results  (skipping  past  other message types). They take the result as
       returned   by   a   call   to   ldap_result(3),   ldap_search_s(3)   or
       ldap_search_st(3).   In  addition  to ldap_parse_result(), the routines
       ldap_parse_sasl_bind_result() and ldap_parse_extended_result() are used
       to  get  all  the result information from SASL bind(2,n,1 builtins) and extended opera-
       tions.

       The errcodep parameter will be filled in(1,8) with the result code from  the
       result message.

       The  server  might supply a matched DN string(3,n) in(1,8) the message indicating
       how much of a name in(1,8) a request was recognized. The matcheddnp  parame-
       ter  will  be  filled  in(1,8) with this string(3,n) if(3,n) supplied, else it will be
       NULL. If a string(3,n) is returned,  it  should  be  freed  using  ldap_mem-
       free(3).

       The  errmsgp  parameter  will be filled in(1,8) with the error(8,n) message field
       from the parsed message. This string(3,n) should be  freed  using  ldap_mem-
       free(3).

       The  referralsp  parameter will be filled in(1,8) with an allocated array of
       referral strings from the parsed message. This array  should  be  freed
       using  ldap_value_free(3).   If no referrals were returned, *referralsp
       is set(7,n,1 builtins) to NULL.

       The serverctrlsp parameter will be filled in(1,8) with an allocated array of
       controls  copied  from  the  parsed  message. The array should be freed
       using ldap_controls_free(3).  If no controls were  returned,  *serverc-
       trlsp is set(7,n,1 builtins) to NULL.

       The  freeit parameter determines whether the parsed message is freed or
       not after the extraction. Any non-zero value will make it free the mes-
       sage.  The ldap_msgfree(3) routine can also be used to free the message
       later.

       For SASL bind(2,n,1 builtins) results, the servercredp parameter will be filled in(1,8) with
       an  allocated  berval  structure  containing  the  credentials from the
       server if(3,n) present. The structure should be freed using ber_bvfree(3).

       For extended results, the retoidp parameter will be filled in(1,8) with  the
       dotted-OID  text  representation  of the name of the extended operation
       response. The string(3,n) should be freed using ldap_memfree(3).  If no  OID
       was returned, *retoidp is set(7,n,1 builtins) to NULL.

       For  extended  results, the retdatap parameter will be filled in(1,8) with a
       pointer to a berval structure containing the  data  from  the  extended
       operation  response. The structure should be freed using ber_bvfree(3).
       If no data were returned, *retdatap is set(7,n,1 builtins) to NULL.

       For all the above result parameters, NULL values can be used  in(1,8)  calls
       in(1,8) order to ignore certain fields.

ERRORS
       Upon  success  LDAP_SUCCESS  is  returned.  Otherwise the values of the
       result parameters are undefined.

SEE ALSO
       ldap(3,5,n)(3), ldap_result(3), ldap_search(3), ldap_memfree(3), ldap_get_val-
       ues(3), ldap_controls_free(3), lber-types(3)

ACKNOWLEDGEMENTS
       OpenLDAP   is   developed   and  maintained  by  The  OpenLDAP  Project
       (http://www.openldap.org/).  OpenLDAP is  derived  from  University  of
       Michigan LDAP 3.3 Release.



OpenLDAP 2.2.15                   2004/07/27              LDAP_PARSE_RESULT(3)

References for this manual (incoming links)