Plug-In Api Reference; Preserving The Default Behavior Of The Server; Bypassing Access Control Checks - Netscape DIRECTORY SERVER 6.2 - PLUG-IN Manual

Plug-In API Reference

This section contains reference information on APIs that enable the following:
•

Preserving the Default Behavior of the Server

•

Bypassing Access Control Checks

Preserving the Default Behavior of the Server
Directory Server implements internal backends for supporting subtrees
cn=config
for the server. For more information about these, check the Netscape Directory Server
Configuration, Command, and File Reference.
It may be required in some cases to let the default behavior of the server be
preserved and not be intercepted by the custom pre-operation plug-ins. To
implement a custom DIOP plug-in without affecting the default behavior of the
Directory Server, a new function named
available. For details about this function, see "Functions Related to Data
Interoperability," on page 548.
Bypassing Access Control Checks
It may be desirable to disable access control checking for operations that are
handled by the custom DIOP plug-in. To enable the plug-ins to bypass access
control, a new flag,
allow a custom plug-in to bypass access control by setting the flag on the
operation-data structure, which is available to the plug-in through the parameter
(
pblock
The following functions have been defined for this purpose:
slapi_operation_set_flag()
slapi_operation_clear_flag()
slapi_is_flag_set()
For details about these functions, see "Functions Related to Data Interoperability,"
on page 548.
, , and
cn=schema cn=monitor
SLAPI_OP_FLAG_NO_ACCESS_CHECK
) setting; see Chapter 16, "Parameter Block Reference."
, which are the reserved naming contexts
slapi_op_reserved()
, has been defined. You
Chapter 13 Using Data Interoperability Plug-Ins
Plug-In API Reference
is being made
167