OK, So I see there is a preprocess module that says you can manipulate attributes:

#  The preprocess module takes care of sanitizing some bizarre
#  attributes in the request, and turning them into attributes
#  which are more standard.

 so I added the following:


   if (User-Password =~ /^(.+)([0-9]{6})$/) {
     update request {
       User-Password = "%{1}"
       Some-PIN-Attr = "%{2}"
     }
   }

Although it did not trim the password and returned Access_Reject (I also saw from the debug that the 6 digit number had not been trimmed) , so I also attempted to add this to the ntlm_auth module with the same result, I am really at a loss here..




On Wed, Apr 17, 2013 at 1:44 PM, Phil Mayers <p.mayers@imperial.ac.uk> wrote:
On 17/04/13 13:00, P. Manton wrote:


Although it complains in the debug (radiusd -XXX) about the following:

Wed Apr 17 12:47:23 2013 : Debug: including configuration file
/etc/freeradius/sites-enabled/default
Wed Apr 17 12:47:23 2013 : Error:
/etc/freeradius/sites-enabled/default[216]: Too many closing braces
Wed Apr 17 12:47:23 2013 : Error: Errors reading
/etc/freeradius/radiusd.conf

Yes, because you just made up syntax.

Look again at the examples you were given, and the examples that come with the server.

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html