RE: [dev] Proposed path to allow LDAP server redundancy

Robert Kehl wrote:

On Tuesday, May 18, 2004 6:21 AM Tyler Hepworth wrote:

...

...

I have included a diff file that contains the modifications made to each file. The basic idea is a foreach loop that loops through a list of servers looking for a valid host. The loop quits as soon as the first active host is found. The list is passed in from Config.pm via a reference to a regular array.

Here is what I put in Config.pm

my @hosts =

('server1.example.com','server2.example.com','server3.example.com','etc' );

...

$Self->{'AuthModule::LDAP::Host'} = \@hosts; $Self->{'Customer::AuthModule::LDAP::Host'} = \@hosts; Host => \@hosts,

Please give me your thoughts on this and whether you think it might be a candidate for inclusion in a future version of OTRS.

Sounds and looks like it should work oob.

One addition, though: If we'd implement it, we'd break existing configurations, which we want to avoid at most costs. Is it possible you implement code to let the user either use a single host or an array?

Ack. Don't want to break things, now do we? I have attached the fix. User's can use the old method $Self->{'AuthModule::...'} = 'ldap@example.com'; or they can pass an array reference: $Self->{'AuthModule::...'} = \@hosts; Easy fix. Hope you like it, Tyler