<div dir="ltr">The #freeradius channel is less than helpful, and I'm not keen on the responses I see in the users mailing list (plus I don't want to sign up for yet another one). So I'm hoping someone on this list has the answer I need:<div><br></div><div>I'm setting up a Freeradius server that authenticates supplicants against an Active Directory system. I have ntlm_auth work, and I can authenticate via Freeradius. So, if I have a user "Jane Doe" with a username "jdoe" then a typical Windows auth request will succeed. That is, the username "foobar\jdoe" will be split into "domain = foobar" and "username = jdoe", and the ntlm_auth will work just fine.</div><div><br></div><div>However, when I have a user like "Tom Doe" with a username like "tdoe" then Windows will send "foobar\tdoe" as the username. When I watch the Freeradius debug output I can see in the mschap processing that it gets a username "foobar doe" sent to it. That clearly won't work.</div><div><br></div><div>Does anyone know how to prevent Freeradius from mangling the name by interpreting escape sequences?<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James Sumners<br><a href="http://james.sumners.info/" target="_blank">http://james.sumners.info/</a> (technical profile)</div><div><a href="http://jrfom.com/" target="_blank">http://jrfom.com/</a> (personal site)</div><div><a href="http://haplo.bandcamp.com/" target="_blank">http://haplo.bandcamp.com/</a> (band page)</div></div></div></div></div>
</div></div>