Manual Pages for UNIX Darwin command on man ldap_parse_extended_result
MyWebUniversity

Manual Pages for UNIX Darwin command on man ldap_parse_extended_result

LDAPPARSERESULT(3) LDAPPARSERESULT(3)

NAME

ldapparseresult - Parsing results

LLIIBBRRAARRYY

OpenLDAP LDAP (libldap, -lldap)

SYNOPSIS

##iinncclluuddee <>

iinntt llddaappppaarrsseerreessuulltt(( LLDDAAPP **lldd,, LLDDAAPPMMeessssaaggee **rreessuulltt,, iinntt **eerrrrccooddeepp,, cchhaarr ****mmaattcchheeddddnnpp,, cchhaarr ****eerrrrmmssggpp,, cchhaarr ******rreeffeerrrraallsspp,, LLDDAAPPCCoonnttrrooll ******sseerrvveerrccttrrllsspp,, iinntt ffrreeeeiitt )) iinntt llddaappppaarrsseessaassllbbiinnddrreessuulltt(( LLDDAAPP **lldd,, LLDDAAPPMMeessssaaggee **rreessuulltt,, ssttrruucctt bbeerrvvaall ****sseerrvveerrccrreeddpp,, iinntt ffrreeeeiitt )) iinntt llddaappppaarrsseeeexxtteennddeeddrreessuulltt(( LLDDAAPP **lldd,, LLDDAAPPMMeessssaaggee **rreessuulltt,, cchhaarr ****rreettooiiddpp,, ssttrruucctt bbeerrvvaall ****rreettddaattaapp,, iinntt ffrreeeeiitt ))

DESCRIPTION

These routines are used to extract information from a result message. They will operate on the first result message in a chain of search results (skipping past other message types). They take the result as returned by a call to llddaapprreessuulltt(3), llddaappsseeaarrcchhss(3) or llddaappsseeaarrcchhsstt(3). In addition to llddaappppaarrsseerreessuulltt(()), the routines llddaappppaarrsseessaassllbbiinnddrreessuulltt(()) and llddaappppaarrsseeeexxtteennddeeddrreessuulltt(()) are used

to get all the result information from SASL bind and extended opera-

tions. The errcodep parameter will be filled in with the result code from the result message. The server might supply a matched DN string in the message indicating

how much of a name in a request was recognized. The matcheddnp parame-

ter will be filled in with this string if supplied, else it will be

NULL. If a string is returned, it should be freed using llddaappmmeemm-

ffrreeee(3). The errmsgp parameter will be filled in with the error message field

from the parsed message. This string should be freed using llddaappmmeemm-

ffrreeee(3). The referralsp parameter will be filled in with an allocated array of referral strings from the parsed message. This array should be freed using llddaappvvaalluueeffrreeee(3). If no referrals were returned, *referralsp is set to NULL. The serverctrlsp parameter will be filled in with an allocated array of controls copied from the parsed message. The array should be freed

using llddaappccoonnttrroollssffrreeee(3). If no controls were returned, *serverc-

trlsp is set 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 llddaappmmssggffrreeee(3) routine can also be used to free the message later. For SASL bind results, the servercredp parameter will be filled in with an allocated berval structure containing the credentials from the server if present. The structure should be freed using bbeerrbbvvffrreeee(3). For extended results, the retoidp parameter will be filled in with the

dotted-OID text representation of the name of the extended operation

response. The string should be freed using llddaappmmeemmffrreeee(3). If no OID was returned, *retoidp is set to NULL. For extended results, the retdatap parameter will be filled in with a pointer to a berval structure containing the data from the extended operation response. The structure should be freed using bbeerrbbvvffrreeee(3). If no data were returned, *retdatap is set to NULL. For all the above result parameters, NULL values can be used in calls in order to ignore certain fields. EERRRROORRSS Upon success LDAPSUCCESS is returned. Otherwise the values of the result parameters are undefined.

SEE ALSO

llddaapp(3), llddaapprreessuulltt(3), llddaappsseeaarrcchh(3), llddaappmmeemmffrreeee(3), llddaappggeettvvaall-

uueess(3), llddaappccoonnttrroollssffrreeee(3), llbbeerr-ttyyppeess(3)

AACCKKNNOOWWLLEEDDGGEEMMEENNTTSS OOppeennLLDDAAPP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OOppeennLLDDAAPP is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.2.19 2004/11/26 LDAPPARSERESULT(3)




Contact us      |      About us      |      Term of use      |       Copyright © 2000-2019 MyWebUniversity.com ™