directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Göktürk Gezer <>
Subject Re: How Authenticators and PasswordPolicies will be managed in new component design.
Date Tue, 10 Jan 2012 00:33:11 GMT
Hi Again,

It seems lots of things are structured like that. Partitions,servers are
all have inner entries.There are partition-indexes and transports those
have same problem. I must develop some way to allow such structure.
Component-hub must have component type specific code to handle these
things. So i'll work on that before everything. But you can still say if
Authenticators must be extensible....


On Tue, Jan 10, 2012 at 1:35 AM, Göktürk Gezer <>wrote:

> Hi Everyone,
> I'm moving through Interceptors to tie them to our new component system.
> As you might guess AuthenticationInterceptor needs some special care. Right
> now, Authenticators and PasswordPolicies are defined as entries under
> AuthenticationInterceptor's entry on DIT. I must say this is not so easy to
> enforce in new system. To make it work that way in component-hub, i have to
> do lots of modifications under many subsystems of component-hub, which is
> not many of us want i guess.
> What i suggest is, introducing Authenticators and PasswordPolicies as new
> extension points to ApacheDS. Authenticators and PasswordPolicies will have
> their own component group under "ou=config". Then we hook them up with the
> AuthenticationInterceptor's instance in runtime, as they are appeared in
> OSGI container. If we do that "ou=config" will look like:
> - ou=config
> --- ou=interceptors
> --- ou=partitions
> --- ou=servers
> --- ou=authenticators
> --- ou=passwordpolicies
> But i don't fully know Authenticators' and PasswordPolicies' nature in
> ApacheDS world. If we don't want them to be extensible but configurable
> under DIT, then we must find them some other place in DIT. Lets talk about
> it...
> Regards,
> Gokturk

View raw message