Re: [xmlblaster] debugging Firebird storage

[Michele <michele at laghi.eu>]

Hi Brad,
the configuration is currently a little odd but I tested it and it works:

Change your xmlBlaster.properties to be the following:

Comment out ALL Security.Server.Plugin* besides the following:
Security.Server.Plugin[ldap][1.0]=org.xmlBlaster.authentication.plugins.ldap.Manager

Comment out the following:
# NONE switches off security checks in passwd file:
#Security.Server.Plugin.htpasswd.secretfile=NONE

Uncomment the following even if you are *NOT* using htpasswd and make
sure the xmlBlaster.htpasswd is empty (this way nobody will be
authenticated with this Plugin which currently is the default one).

Security.Server.Plugin.htpasswd.secretfile=${user.home}${file.separator}xmlBlaster.htpasswd
#Security.Server.Plugin.htpasswd.allowPartialUsername=false

Comment out the htpasswd :
#Security.Client.DefaultPlugin=htpasswd,1.0

and add:

Security.Client.DefaultPlugin=ldap,1.0

This way clients will take the ldap as the default.

I tested it right now and it works. In the future we may change the
configuration to make it more simple: I did'nt get it myself anymore ;)

Regards
Michele



Brad Clements wrote:
> On 11 Oct 2006 at 16:15, Michele wrote:
> 
>> Nothing odd with a): if the server offers different authorization
>> methods it is a nice feature. b) of course shall not be required. The
>> hot potato at the moment is the fact that clients are allowed to log
>> in even if 'simple' is not activated on the server side. I am looking
>> at this issue right now and will come back.
> 
> What would work for me is  at type="default" and let the server config determine 
> what method "default" is.
> 
> I could get by with htpasswd now, but need to be able to move to ldap in the near 
> future. I cannot redeploy client code when the changover to ldap occurs, and I do 
> not trust my client machines.. :-(
> 
> 
> 
> 
> 
>