HP-UX Directory Server 8.1 plug-in reference

Table Of Contents
4. set args -D /etc/opt/dirsrv/slapd-instance_name \
-i /var/opt/dirsrv/slapd-instance_name/run/slapd-instance_name.pid -d 0
5. break user-defined-function-in-the-plugin
6. run
13.5 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”
13.5.1 Preserving the default behavior of the server
Directory Server implements internal back ends for supporting subtrees cn=config, cn=schema,
and cn=monitor, which are the reserved naming contexts for the server. For more information
about these, see the HP-UX 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 preoperation plug-ins. To implement a custom DIOP plug-in without
affecting the default behavior of the Directory Server, a new function named
slapi_op_reserved() is being made available. For details about this function, see
Chapter 49 “Functions related to data interoperability”.
13.5.2 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,
SLAPI_OP_FLAG_NO_ACCESS_CHECK, has been defined. You 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) setting; see Part V “Parameter block reference”.
The following functions have been defined for this purpose:
“slapi_operation_set_flag()”
“slapi_operation_clear_flag()”
“slapi_operation_is_flag_set()”
For details about these functions, see Chapter 49 “Functions related to data interoperability”.
114 Using data interoperability plug-ins