Guillaume Rousse wrote:
What's wrong with just looking recursively for the name under which the
module has been instanciated in the authorization section, without
interpreting fail-over behaviour at all ?
Because it may be listed under multiple Auth-Type sections. This is
something that
Alan DeKok a écrit :
Guillaume Rousse wrote:
It is not documented in the rlm_ldap file shipped in top-level directory
(at least for release 2.0.0). The fact that there is a huge redundancy
between this file and comments in default configuration files doesn't
help maintaining a reference
Hello list.
I've recently upgraded my freeradius servers from 1.1.7 to 2.0.0, and
I've been hit badly by the change in the handling of LDAP-UserDn
attribute, as detailed in
http://www.nabble.com/Re%3A-LDAP-Groups-and-EAP-p14886209.html
I think this ought to be documented in rlm_ldap
Guillaume Rousse wrote:
I've recently upgraded my freeradius servers from 1.1.7 to 2.0.0,
2.0.3 has been out for a while...
and
I've been hit badly by the change in the handling of LDAP-UserDn
attribute, as detailed in
http://www.nabble.com/Re%3A-LDAP-Groups-and-EAP-p14886209.html
This
Alan DeKok a écrit :
I think this ought to be documented in rlm_ldap documentation (as well
as minor other changes, such as the new tls subsection).
The new tls sub-section isn't required. The old-style configuration
*should* work.
It does. But clarification between what's old and what's
Guillaume Rousse wrote:
It does. But clarification between what's old and what's new syntax
doesn't harm.
The new syntax is documented, and is preferred. If you try the old
one (undocumented and deprecated), it works. What needs clarification?
Right, but that seems to be only a syntax
Alan DeKok a écrit :
Guillaume Rousse wrote:
It does. But clarification between what's old and what's new syntax
doesn't harm.
The new syntax is documented, and is preferred. If you try the old
one (undocumented and deprecated), it works. What needs clarification?
It is not documented
Guillaume Rousse wrote:
It is not documented in the rlm_ldap file shipped in top-level directory
(at least for release 2.0.0). The fact that there is a huge redundancy
between this file and comments in default configuration files doesn't
help maintaining a reference documentation.
The
8 matches
Mail list logo
