Getting And Setting Parameters For The Bind Operation; Processing An Ldap Unbind Operation - Netscape DIRECTORY SERVER 6.02 - PLUG-IN Manual

Table of Contents

Advertisement

Your pre-operation and post-operation bind functions should return 0 if successful.
If the pre-operation function returns a non-zero value, the post-operation bind
function is never called.
For information on defining a function that handles authentication, see Chapter 8,
"Defining Functions for Authentication."
Getting and Setting Parameters for the Bind
Operation
The front-end makes this information available to pre-operation and
post-operation plug-in functions in the form of parameters in a parameter block.
Parameter ID
SLAPI_BIND_TARGET
SLAPI_BIND_METHOD
SLAPI_BIND_CREDENTIALS
SLAPI_BIND_RET_SASLCREDS
SLAPI_BIND_SASLMECHANISM
Note that if the
authentication was used and simple credentials were provided.

Processing an LDAP Unbind Operation

When the Directory Server receives an LDAP unbind request from a client, the
front-end calls the unbind function for each back-end. No operation-specific
parameters are placed in the parameter block that is passed to the unbind function.
In the parameter block, the following parameters specify plug-in functions that are
called in the process of executing an unbind operation:
Data Type
Description
DN of the entry to bind as.
char *
Authentication method used, for example,
int
LDAP_AUTH_SIMPLE or LDAP_AUTH_SASL.
Credentials from the bind request.
struct
berval *
Credentials that you want sent back to the client.
struct
Set this before calling
berval *
slapi_send_ldap_result().
SASL mechanism used, for example,
char *
LDAP_SASL_EXTERNAL.
SLAPI_BIND_SASLMECHANISM
Processing an LDAP Unbind Operation
parameter is empty, simple
Chapter 7
Defining Functions for LDAP Operations
79

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 6.02

Table of Contents