I wonder if the solution lies in tweaking the provider to allow users to enter their AD username without the domain prefix, but to store the username with the domain. In a multi domain environment, you may have to present the user with an option dropdown with the various domains in and let the user choose.

All of our DNN sites run inside a very large multinational and we have not really had a problem with users forgeting the domain prefix.  But then most users who "manually" login this way are logging as admins or editors and have been trained. Normal users would be automatically logged in so domain/username entry is irrelevant.

Also :

- you can always edit the "Login Failure" message to say "enter users name in the format "domain\username".

- there comes a logical point where you may have to have separate DNN installs to cater for different cross sections of users.

- I do believe there is some effiency in an AD environoment in a single username. We have  a couple of installs with 10-15 portals. In a very large enterprise where we can have up to +15,000 users per portal, that's a lot of redundant storage taken up for the same user records if they had their own entries.

Cheers

Ian

Are you having this problem with the AD provider or with the regular DNN provider Brian?

I don't know if it was a Partner call, Fusion call, or otherwise, but I'm pretty sure that someone in DNN mentioned multi-portal user sharing being an upcoming feature. This was a couple of months ago at least, but I haven't seen or heard any mention of it since.