Table of Contents
Advertisement
How Directory Server Plug-Ins Work
•
You can design an action that the Directory Server performs after the server
successfully completes an LDAP operation. For example, you can send mail to
a client after an LDAP operation is successfully completed.
•
You can define extended operations, as defined in the the LDAP v3 protocol.
•
You can provide alternate matching rules when comparing certain attribute
values.
How Directory Server Plug-Ins Work
When properly configured, the Directory Server will load your plug-in on startup.
Once loaded, the Directory Server will resolve calls made to your plug-in functions
as it processes the LDAP requests contained in your applications.
Internally, the Directory Server has hooks that allow you to register your own
functions to be called when specific events occur. For example, the Directory Server
has hooks to call a registered plug-in in the following situations:
•
Before preforming an LDAP operation (for example, before an entry is added
to the directory)
•
When adding, modifying, removing, renaming, or searching for entries in the
database
•
After performing an LDAP operation (for example, after an entry is added to
the directory)
•
Before writing an entry to the database
•
After reading an entry from the database
•
When processing an extended operation
•
When indexing an attribute
•
When filtering search result candidates based on an attribute
When you register your plug-in functions, you specify the function type and the
plug-in type. Together, these specifications indicate when the function is called. For
more information on this topic, refer to the section "Types of Directory Server
Plug-Ins" on page 24.
20
Netscape Directory Server Plug-In Programmer's Guide • May 2002
Advertisement
Table of Contents
