Comment 25 for bug 534629

Revision history for this message
Alexander Brinkman (abrinkman-gmail) wrote :

Can confirm the fix works also for me.

However I do see a change in how username checks are handled. Before the AssumeDefaultDomain setting worked I could match 'domain\username' in group and sudo checks without problems. It didn't matter how the username was actually registered in AD (i.e. 'DOMAIN\UserName' or 'DOMAIN\USername', etc.). Now, with AssumeDefaultDomain on, I can logon with either 'USername', 'UserName' or 'username', but sudo and group check only work for the name that is used in AD. I.e. 'UserName' would match, but 'username' would not. But perhaps this behaviour was there before?