...
- org.apache.directory.server.core.normalization.NormalizationInterceptor
- org.apache.directory.server.core.authn.AuthenticationInterceptor
- org.apache.directory.server.core.referral.ReferralInterceptor
- org.apache.directory.server.core.authz.AciAuthorizationInterceptor
- org.apache.directory.server.core.authz.DefaultAuthorizationInterceptor
- org.apache.directory.server.core.exception.ExceptionInterceptor
- org.apache.directory.server.core.changelog.ChangeLogInterceptor
- org.apache.directory.server.core.operational.OperationalAttributeInterceptor
- org.apache.directory.server.core.schema.SchemaInterceptor
- org.apache.directory.server.core.subtree.SubentryInterceptor
- org.apache.directory.server.core.collective.CollectiveAttributeInterceptor
- org.apache.directory.server.core.event.EventInterceptor
- org.apache.directory.server.core.trigger.TriggerInterceptor
- org.apache.directory.server.core.journal.JournalInterceptor
Interceptors should usually pass the control of current invocation to the next interceptor by calling an appropriate method on NextInterceptor. The flow control is returned when the next interceptor's filter method returns. You can therefore implement pre-, post-, around- invocation handler by how you place the statement.
Interceptors are a powerful way to extend and modify the server behavior. But be warned. A mistakenly written interceptor may lead to a dis-functional or corrupt server.
Password hash. A simple interceptor
...