Netscape DIRECTORY SERVER 7.0 - PLUG-IN Manual page 175

In the following table, the various required elements of the pre-operation plug-in
are identified by the function calls used in the
use and simplify understanding).
Table 13-2 Elements of Pre-Operation Plug-in
Description of the
Plug-in
Initialization of the
Plug-in by the Server
Reserved Naming
Contexts
(cn=schema,
cn=config,
cn=monitor)
#define PLUGIN_NAME
static Slapi_PluginDesc plugindesc = { PLUGIN_NAME,
"Netscape", "6.1",
plugin"
}
nullsuffix_init( Slapi_PBlock *pb )
In this function, all the callbacks are set up and will be called by the server for
each LDAP operation.
Flag used for LDAP operation
SLAPI_PLUGIN_PRE_SEARCH_FN
SLAPI_PLUGIN_PRE_ADD_FN
SLAPI_PLUGIN_PRE_MODIFY_FN
SLAPI_PLUGIN_PRE_DELETE_FN
SLAPI_PLUGIN_PRE_BIND_FN
SLAPI_PLUGIN_PRE_MODRDN_FN
slapi_op_reserved(pb) is called to determine whether the operation
should be handled internally by
base on which the operation is applied is a reserved naming context. If
slapi_op_reserved() returns a non-zero value, the plug-in does not
attempt to handle that operation. It is done by the following code snippet:
if( slapi_op_reserved(pb) ){
return PLUGIN_OPERATION_IGNORED;
}
See testdatainterop.c for details.
The slapi_op_reserved() function, which can be used for reserving some of
the naming contexts in the Directory Server (cn=schema, cn=config,
cn=monitor), is called first in the database plug-in and then the call for turning
off access control.
testdatainterop.c
"nullsuffix-preop"
"sample pre-operation null suffix
Callback
nullsuffix_search
nullsuffix_add
nullsuffix_modify
nullsuffix_delete
nullsuffix_bind
nullsuffix_modrdn
Directory Server
Chapter 13 Using Data Interoperability Plug-ins
Sample DIOP Plug-in
(to illustrate the
; for example, whether the
175