NAME
saslcallbacks - How to work with SASL callbacks
SYNOPSIS
##iinncclluuddee <
> DESCRIPTION
ssaassllccaallllbbaacckkss are used when the application needs some information from the application. Common reasons are getting for getting usernames and passwords. A client MUST specify what callbacks they support in the saslclient/serverinit() or saslclient/servernew() calls. If an authentication mechanism needs a callback that the application does not state it supports it cannot be used. If a callback has an iidd parameter that should be checked to make sure you are giving the appropriate value. If an application is using the client side of the library functions to handle the callbacks are not necessary. Instead the application may deal with callbacks via SASLINTERACT's. See saslclientstart/step() for more information. The list of callbacks follows: CCoommmmoonn CCaallllbbaacckkss saslgetoptt Get an option value sasllogt Log message handler saslgetpatht Get path to search for mechanisms saslverifyfilet Verify files for use by SASL saslcanonusert Username canonicalization function.CClliieenntt-oonnllyy CCaallllbbaacckkss
saslgetsimplet Get user/language list saslgetsecrett Get authentication secret saslchalpromptt Display challenge and prompt for response saslgetrealmt Get the realm for authenticationSSeerrvveerr-oonnllyy CCaallllbbaacckkss
saslauthorizet Authorize policy callback saslserveruserdbcheckpasst verify plaintext password saslserveruserdbsetpasst set plaintext password RREETTUURRNN VVAALLUUEE SASL callback functions should return SASL return codes. See sasl.h for a complete list. SASLOK typically indicates success. CCOONNFFOORRMMIINNGG TTOO RFC 2222SEE ALSO
sasl(3), saslerrors(3), saslauthorizet(3), sasllogt(3), saslget-
patht(3), saslverifyfilet(3), saslcanonusert(3), saslgetsim-
ple(3), saslgetsecrett(3), saslchalpromptt(3), saslgetrealmt(3), saslauthorizet(3), saslserveruserdbcheckpasst(3), saslserveruserdbsetpasst(3) SASL man pages SASL saslcallbacks(10 July 2001)