>
> * Remove the server requirement that one of User-Password
> or CHAP-Password exist when doing authentication. These
> checks should be handled by the modules. This change
> also prepares us for EAP.
> Patch from Raghu <[EMAIL PROTECTED]>
Does this mean that chap authentication is fully supported now?
I cant seem to get chap users to auth from ldap..
Thanks.. Mike
rad_recv: Access-Request packet from host 137.236.215.1:3793, id=188,
length=92
User-Name = "mdh"
CHAP-Password =
"\256\212\321\205\0171\211\024\213\263\013\372\216l\017\210"
CHAP-Challenge = "\221\302z\324\337Pv\274\240/8\350/\0275\345"
Service-Type = Authenticate-Only
Framed-Protocol = PPP
NAS-IP-Address = 137.236.215.1
NAS-Port = 22844
NAS-Port-Type = Virtual
rlm_ldap: - authorize
rlm_ldap: performing user authorization for mdh
rlm_ldap: looking for check items in directory...
rlm_ldap: looking for reply items in directory...
rlm_ldap: user mdh authorized to use remote access
rlm_ldap: - authenticate
rlm_ldap: Attribute "Password" is required for authentication. Cannot use
"CHAP-Password".Login incorrect:
[mdh/<CHAP-Password>] (from nas 137.236.215.1 port 22844)
Sending Access-Reject of id 188 to 137.236.215.1:3793
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
