Project

General

Profile

Actions

Feature #464

closed

mulitple ldap hostnames

Added by Anonymous over 18 years ago. Updated over 15 years ago.

Status:
Fixed
Priority:
Low
Category:
mod_auth
Target version:
-
ASK QUESTIONS IN Forums:

Description

For failover it would be nice to be able to enumerate more than one ldap server name, like most other clients allow.

-- bkw

Actions #1

Updated by Anonymous about 18 years ago

Ahem... it seems this is already possible.
I just tried:


 "auth.backend.ldap.hostname = "bogus.example.com real.ldap.server.com" 

and it worked!

Not sure if this will also handle failover after connecting, but I'll do some testing
.
We should document this, probably...

-- bkw

Actions #2

Updated by Anonymous about 18 years ago

OK, it seems to work like this (lighttpd-1.4.10 + cgi-patch):

  • During startup the first working ldap server is chosen.
  • If that server should go down, no failover takes place
  • moreover, even if the ldap server comes back, lighty needs a restart to reconnect. Not sure how this relates to Ticket #294 and the LDAP reconnect patch...

Should I open a new ticket?

-- bkw

Actions #3

Updated by deepunix over 16 years ago

because it's a standard feature of ldap library, see ldap_init(3).

Replying to bkw:

Ahem... it seems this is already possible.
I just tried: {{{
"auth.backend.ldap.hostname = "bogus.example.com real.ldap.server.com"
}}}

and it worked!

Actions #4

Updated by stbuehler over 15 years ago

  • Status changed from New to Fixed
  • Resolution set to duplicate

Duplicate of ldap reconnect problem.

Actions

Also available in: Atom