Show Table of Contents
Chapter 10. Writing Extended Operation Plug-ins
This chapter explains how to write plug-in functions to handle extended operations. Extended operations are defined in the LDAP v3 protocol.
10.1. How Extended Operation Plug-ins Work
You can define your own operation that you want the Red Hat Directory Server to perform. If you create a custom extended operation, you assign an object identifier (OID) to identify that operation. LDAP clients request the operation by sending an extended operation request. Within the request, the client specifies:
- The OID of the extended operation.
- Data specific to the extended operation.
When the Directory Server receives the request, the server calls the plug-in registered with the specified OID. The plug-in function has access to both the OID and the data in the client's request. The plug-in function can send a response back to the client containing an OID plus any additional data that might be needed.
In order to use extended operations, you need to configure both the Directory Server and the client so that they understand the specific extended operation that you want to perform.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.