On Fri, 25 Jun 2004 [EMAIL PROTECTED] wrote:
Ah. But the module still registers a callback for LDAP-Group, even
if one already exists. That should probably be double-checked...
The only way for the ldap module to know if ldap-group has been registered is to
keep a
to validate the user.
Login incorrect: [EMAIL PROTECTED] (from client Self port 123)
Delaying request 0 for 1 seconds
Finished request 0
So the user never gets authenticated.
I saw that kostas made a change to rlm_ldap in 1.0.0 pre for instanciated
ldap_groupcmp() is that my solution?
Regards
Markus
[EMAIL PROTECTED] wrote:
Now, when a user tries to get authenticated the ldap_groupcmp() always
uses one ldap instance even when the auth-type for the user is a
different ldap-instance.
The LDAP module registers a callback for LDAP-Group, and does not
provide a way to configure more than one
On Thu, 24 Jun 2004, Alan DeKok wrote:
[EMAIL PROTECTED] wrote:
Now, when a user tries to get authenticated the ldap_groupcmp() always
uses one ldap instance even when the auth-type for the user is a
different ldap-instance.
The LDAP module registers a callback for LDAP-Group, and does
Kostas Kalevras [EMAIL PROTECTED] wrote:
* Apr 2004, Kostas Kalveras [EMAIL PROTECTED]
- Add a per instance Ldap-Group attribute (of the form
instance-Ldap-Group) and register
a corresponding ldap_groupcmp function
So in other words, it's in there already...
Ah. But the module
On Thu, 24 Jun 2004, Alan DeKok wrote:
Kostas Kalevras [EMAIL PROTECTED] wrote:
* Apr 2004, Kostas Kalveras [EMAIL PROTECTED]
- Add a per instance Ldap-Group attribute (of the form
instance-Ldap-Group) and register
a corresponding ldap_groupcmp function
So in other words,
6 matches
Mail list logo