Mike Horton wrote
Are you still using impersonation or have you turned that off? That's the only other thing I can think of.
Yes that's how they're added to the database. John Hoskins has donated code that will strip the domain name out and I may include it in the next release but I want to go over all the ramifications of someone doing so after already running a site with the domain added in, what to do if there's a username duplication (ie: I've got an internet/extranet site and Mike Hollow has registered as an extranet user using MikeH as a username. What's going to happen when the domain name is stripped from my user account which is DOMAIN\MikeH).
I was thinking about this issue a bit lately... Basically it boils down to the fact that DNN stores regular users in the user database as "username", while it stores domain users as "domain\username", so in that case there would be a conflict of usernames if the "domain\" part was stripped out. I could see this happening quite often in a mixed-mode system, and while I believe the domain account should have precedence, it could cause quite a problem if the original user was quite active.
So, instead of stripping off the domain name "before" it goes into the database, how about leaving it there and stripping it when needed? How about if DNN stored normal users as "DNN\username" by default, and stripped it off during display, login, etc...? In other words, you need to be able to maintain two different accounts with the same username, and the only way to differentiate between the two is whether they are a DNN account or a DOMAIN account. This might also allow for future expansion, where you could have multiple domains, different types of logins, etc., all designated by their username prefix.
Just a thought...