Writing Pre/Post-Operation Plug-ins
This chapter explains how to write functions that the Netscape Directory Server
(Directory Server) calls before and after executing an LDAP operation. These
functions are called pre-operation and post-operation plug-in functions.
•
How Pre/Post-Operation Plug-ins Work (page 81)
•
Types of Pre-Operation and Post-Operation Functions (page 83)
•
Registering Pre/Post-Operation Functions (page 86)
How Pre/Post-Operation Plug-ins Work
The Directory Server can perform the following LDAP operations:
search
NOTE
You can configure the Directory Server to call your custom plug-in functions before
and after executing any of these LDAP operations.
For example, you can write a pre-operation function that validates an entry before
the server performs an LDAP
plug-in function would be one that sends a notification to a user after their entry
has been modified by an LDAP
,
,
,
modify
add
delete
The Directory Server can also perform extended operations as
defined in the LDAPv3 protocol. For information on implementing
plug-in functions to execute extended operations, see chapter 10,
"Writing Extended Operation Plug-ins."
,
,
modifyRDN
compare
operation. An example of a post-operation
add
operation.
modify
Chapter 6
,
bind
, and
.
abandon
,
unbind
81
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 7.0 - PLUG-IN and is the answer not in the manual?