Dean, Barry wrote:
I am working on a new radius config and have been trying to avoid the lookup
in LDAP I have been seeing for the outer identity.
I have moved to 2.1.8 with the inner-tunnel virtual host enabled.
I have an authorise section for the relevant virtual server that has:
On 13 May 2010, at 06:54, Alan DeKok wrote:
Dean, Barry wrote:
I am working on a new radius config and have been trying to avoid the lookup
in LDAP I have been seeing for the outer identity.
I have moved to 2.1.8 with the inner-tunnel virtual host enabled.
I have an authorise section
Dean, Barry wrote:
...
[ldap] performing search in OU=UOL,DC=adserer,DC=liv,DC=ac,DC=uk, with
filter (sAMAccountName=user)
[ldap] looking for check items in directory...
[ldap] looking for reply items in directory...
WARNING: No known good password was found in LDAP. Are you sure that the
sigh
Dean, Barry wrote:
...
[ldap] performing search in OU=UOL,DC=adserer,DC=liv,DC=ac,DC=uk, with
filter (sAMAccountName=user)
[ldap] looking for check items in directory...
[ldap] looking for reply items in directory...
WARNING: No known good password was found in LDAP. Are you sure
On 13 May 2010, at 10:15, Alan DeKok wrote:
Dean, Barry wrote:
...
[ldap] performing search in OU=UOL,DC=adserer,DC=liv,DC=ac,DC=uk, with
filter (sAMAccountName=user)
[ldap] looking for check items in directory...
[ldap] looking for reply items in directory...
WARNING: No known good
Dean, Barry wrote:
The issue is that the self same configuration in FreeRADIUS 2.0.2 works! But
with 2.1.8 it fails.
Yes... the behavior changed slightly in the past 2 years.
Read raddb/modules/ldap in 2.1.8. Look for auth_type. This is
documented.
FR 2.0.2 reports
I am working on a new radius config and have been trying to avoid the lookup in
LDAP I have been seeing for the outer identity.
I have moved to 2.1.8 with the inner-tunnel virtual host enabled.
I have an authorise section for the relevant virtual server that has:
authorize {
On Thu, 25 Mar 2004, Wolfgang Hottgenroth wrote:
Hi,
I've a question concerning the rlm_ldap module.
The order of radius attributes, especially of multiple values for one
attribute, in the access-accept reply sent to the NAS is sometimes
crucially. For instance for the ascend-data-filter
Hi,
I've a question concerning the rlm_ldap module.
The order of radius attributes, especially of multiple values for one
attribute, in the access-accept reply sent to the NAS is sometimes
crucially. For instance for the ascend-data-filter attribute.
Is there a way to guarantee this order when
9 matches
Mail list logo