Upgrade to v2.1.9 - ntdomain logon issues

[Extra Fu]

On Wed, Sep 8, 2010 at 2:35 PM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk> wrote:
> Hi,
>
>> [copy.user-name]        expand: %{User-Name} -> SMB001\bob
>> copy.user-name: Added attribute Stripped-User-Name with value 'SMB001\bob'
>> ++[copy.user-name] returns ok
>> [add-dollar-sign]       expand: ^(host/.*) -> ^(host/.*)
>> add-dollar-sign: Does not match: Stripped-User-Name = SMB001\bob
>> ++[add-dollar-sign] returns ok
>> [strip-realm-name]      expand: ^(.*[\/]+) -> ^(.*[\/]+)
>> strip-realm-name: Changed value for attribute Stripped-User-Name from
>> 'SMB001\bob' to 'bob'
>> ++[strip-realm-name] returns ok
>
> WARNING - ALERT - WARNING
>
> those particular filters look way way too familiar to me.  they look like
> some kind of FreeRADIUS 1.0.x hack that I would have told someone to put into
> their config back in around 2007 or so.
>
> you do not need that sort of stuff in FreeRADIUS 2.x

Well, the User-Name attribute is being copied to Stripped-User-Name
which is *only* used during LDAP authentication, which works.

Why would it interfere with User-Name?

Thanks!