Configuring FreeRADIUS to use ntlm_auth

A.L.M.Buxey at lboro.ac.uk A.L.M.Buxey at lboro.ac.uk
Mon Sep 17 22:29:23 CEST 2007


Hi,

> NULL
>     rlm_realm: No such realm "NULL"
>   modcall[authorize]: module "suffix" returns noop for request 0
>   rlm_eap: No EAP-Message, not doing EAP
>   modcall[authorize]: module "eap" returns noop for request 0
>     users: Matched entry DEFAULT at line 154
>   modcall[authorize]: module "files" returns ok for request 0
> rlm_pap: WARNING! No "known good" password found for the user. 
> Authentication may fail because of this.
>   modcall[authorize]: module "pap" returns noop for request 0
> modcall: leaving group authorize (returns ok) for request 0
>   rad_check_password:  Found Auth-Type System
> auth: type "System"
>   Processing the authenticate section of radiusd.conf
> modcall: entering group authenticate for request 0
>   modcall[authenticate]: module "unix" returns notfound for request 0
> modcall: leaving group authenticate (returns notfound) for request 0

but this didnt even attempt to use ntlm_auth! and can you see where
it is failing?  is it not clear?  

rad_check_password:  Found Auth-Type System

this means its being told to use system authentication. ie in 'user' file
you have DEFAULT Auth-Type := System  REMOVE that line if you dont use unix password
authentication!

modcall[authenticate]: module "unix" returns notfound for request 0

see? unix check failed. thus it all stops because its been told to use
Auth-Type System

alan



More information about the Freeradius-Users mailing list