Hello everyone! Since this is my first post on this list, I want to say thank you for your great project!
We want to use ApacheDS as a proxy to another LDAP server and try to adapt the examples for writing custom interceptors. Can you help us with the following questions? (1) Is there a preferred way of registering the new interceptor? There seems to be some kind of lifecycle management, someone needs to call the “init” method of the interceptor. When adding the new interceptor the the directory service’s interceptors list by “setInterceptors” the init method is not invoked. We also tried “addAfter” but that method does something slightly different. I think it would be nice to have one main entry point for adding new interceptors. BTW: “addAfter” of “DefaultDirectoryService” contains a bug. It adds the new interceptor /before/ and not after another interceptor. (2) Why does AuthenticationInterceptor not pass “bind” to the next interceptor? Is there a minimum set of interceptors that are absolutely needed for the LDAP server to work correctly? As AuthenticationInterceptor also deals with creating a session I would like to reuse the code. But when I add my proxy interceptor after AuthenticationInterceptor it will not be invoked for “bind”. (3) What class of ApacheDS is responsible for creating the messageId and at which point is it created? (4) Can we also use Github for contributions? We already have Github accounts so that would be much easier for us. 😊 Thank you very much and best regards, Christopher
