I already posted a question about a way to specify a default domain so that my user's will not have to specify their login as domain\userid.  I got some responses that all involved modifying the code, but I haven't done it because ultimately, it just won't work the way I want.  Here is my situation.  I want our normal employees to be able to use their AD user accounts, but of course still need access to host/admin accounts.  In addition, for some user's, I plan to create an additional (in addition to their AD account) admin type account so that they can admin the portal.  But, most of the time they use the portal, I want the screens to look like it would for a normal user.  Because of these additional accounts, it just doesn't make sense for me to go hack the code by adding hardcoded user accounts to have different authentication.

What would work great is if:

1.  I could specify a default domain.

2.  I could specify the order of authentication...internal then AD, or AD then internal.

This way, I could say, try to login internally first.  If that fails, then try with this default domain.  Of course, the reverse order works too, but that order would be my preference.  I have been working on a 3rd party application and because they allowed the product to specify the order of authenticators, it makes it very flexible.

Thanks.

Can you point me to the best post of yours that covers this?

Thanks.

I create a login module that do that, but I developed with DNN3.1 and TTT runtime. In the TTT runtine I've made some change to support multiples AD domian because I need to allow user from two AD forest to login in the same site.

Now I'm looking for a solution in the DNN4 but I don't like to make change in the original code, I waiting to TAM  to develop this change in the core modules.

Regards.

Alejandro