I'm using Module Active Directory 05.00.04 in a Dotnetnuke 7.0 installation on a windows 2008 server.

I have some users created in my windows 2008 active directory, like User1 and User2, and when i login the site using Windows Autentication AD button, the users are created in Dotnetnuke if they do not exist yet.

 So far so good.

The problem is that when i login using "DOMAIN\User1", dotnetnuke creates a user called "DOMAIN\User1" and when i login using just "User1" without the DOMAIN, dotnetnuke creates another user called just "User1".

In the end i get two users registered in dotnetnuke that point to the same and only user in the active directory.

Is this a normal behaviour? It would be more consistent if dotnetnuke just created only one user and allowed me to login with or without the "DOMAIN\" referencing the AD user "User1".

 

 

 

Oh... can you log it as an issue on http://dnnauthad.codeplex.com so that I have a reminder to check it out over the holidays. Thanks.

I Mike,

 i've checked if i have the default domain property in the AD module and i've tested it again with the following results:.

 If i have the default domain property set, Dotnetnuke doesn't create two accounts but if i have no default domain set, Dotnetnuke creates the two diferent accounts (with and without DOMAIN\).

In my opinion, the default domain property is OK and is usefull, but if you allow users to login in this particular case:

1. Without having the "DOMAIN\" set in the module property "default domain", performing login also without specifying the "DOMAIN\" as just "DNN7User1".  

...this would cause two users being created, whenever the module administrator change the "default domain" property.

You shouldn't allow users to login and create then, if the default domain property is not set in the module property and the user don't specify the DOMAIN\ in the moment of the login.

What do you think Mike?

Thanks