|Linux & Unix Commands - Search Man Pages
sasl_callbacks(10 July 2001) sasl_callbacks(10 July 2001)
sasl_callbacks - How to work with SASL callbacks
sasl_callbacks 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 sasl_client/server_init() or sasl_client/server_new() 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 id parameter that should be checked to make sure you are giving the
If an application is using the client side of the library functions to handle the call-
backs are not necessary. Instead the application may deal with callbacks via SASL_INTER-
ACT's. See sasl_client_start/step() for more information.
The list of callbacks follows:
Get an option value
Log message handler
Get path to search for mechanisms
Verify files for use by SASL
Username canonicalization function.
Get user/language list
Get authentication secret
Display challenge and prompt for response
Get the realm for authentication
Authorize policy callback
verify plaintext password
set plaintext password
SASL callback functions should return SASL return codes. See sasl.h for a complete list.
SASL_OK typically indicates success.
sasl(3), sasl_errors(3), sasl_authorize_t(3), sasl_log_t(3), sasl_getpath_t(3), sasl_veri-
fyfile_t(3), sasl_canon_user_t(3), sasl_getsimple(3), sasl_getsecret_t(3), sasl_chal-
prompt_t(3), sasl_getrealm_t(3), sasl_authorize_t(3), sasl_server_userdb_checkpass_t(3),
SASL man pages SASL sasl_callbacks(10 July 2001)
All times are GMT -4. The time now is 01:43 PM.