Hello All,
I'm using 2.16.1 (including patches) and AuthLDAPSDK for LDAP
authentication. My config file contains several handlers (different
Called-Station-Id's), but which all authenticate against the same LDAP
server. When testing with the same user/password the following showed up:
handler 1 could not authenticate
handler 2 could authenticate
I know there is some 'bug' in the LDAPSDK module not noting when the LDAP
connection is reset by some means.
Questions:
According to the manual a new LDAP connection is set up each time a request
is initiated. I thought that LDAPSDK does not do this but reuses the LDAP
connection for several subsequent requests (long time ago I've been sniffing
and saw one connection setup and several LDAP requests following, this was
with Radiator 2.14.1). Anybody knows this for sure?
Does Radiator setup a new/separate LDAP connection to the same LDAP server
if a different Handler is authenticating? This question relates to the
former one, as I still presume Radiator sets up an LDAP connection once
using LDAPSDK and tries to reuse this one.
Regards,
Karel van der Velden
----------------------------------------------------------------------------
---
Karel van der Velden | Telephone : +31 50 5851003
KPN Telecom | Telefax : +31 50 5853454
ICT/BPG P&C 2 | E-mail : [EMAIL PROTECTED]
P.O. Box 188 | DISCLAIMER: This Statement is not an
official
NL-9700 AD Groningen | statement from, nor does it represent an
The Netherlands | official position of, KPN Telecom
----------------------------------------------------------------------------
---
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
