I wanted to applaud you guys on a piece of functionality one of my users fell into.  Reading the documentation I figured we were limited to AD logons using the "domain\username" syntax but I've now sucessfully seen the authentication happen in "username@domain.com" syntax as well.  Our User Names and e-mail address aliases match company-wide, so I believe this will be our login syntax of choice over the documented method that has caused a small learning-curve so far.

Now, I want to make sure this isn't identified as a bug and slated to be removed in a future version!  We have been so happy with the flexibility of the login options with being able to utilize Active Directory while including non-Active Directory users in the same portal, and this is just another level of satisfaction.

One issue that I do see however is that a different account is created in DNN for each login syntax used.  On one portal we have the entire contents are restricted to only a few AD users (and non-AD users) so that in order to see anything you had to be added to a specific non-standard role by the administrator.  I proactively created an account for an AD user (also a nice feature, so the junk I put in as a password like "useyournetworkpassword" isn't actually used at the time of login).  The user chose the e-mail style syntax (through lack of knowledge) and was able to log on as they were identified as an AD user, but a new account was created in DNN and wasn't automatically added to the role.  The long and short of all this--can this behavior be changed so that no matter the syntax, the login is matched with a single DNN account that matches the AD account?