We have a situation where whe have a large domain partitioned into virtual domains using different UPN extentsions.  This allows for the duplication of the user name portion of the logon id (in front of the @) across different UPN extensions.  But, to make this work, the pre-Windows 2000 logon id has to have a user name portion that is unique in the domain.  What we have found (in 2.0.12 as well) is that if the username portion of the UPN logon id does not match the NT4 compatible username, authentication via UPN logon fails.  We addressed this previously by making the necessary changes to the 2.0.12 source.

For instance, the items below represent 3 different users in the same domain:

User1, John Smith:

UPN logon: jsmith@abc.com
PreWin2K logon: DOMAIN\jsmith.abc
 

User2, also John Smith:

UPN logon: jsmith@xyz.com
PreWin2K logon: DOMAIN\jsmith.xyz

User3, also John Smith:

UPN logon: jsmith@DOMAIN.com
PreWin2K logon: DOMAIN\jsmith
 

In these 2 examples, using the 3.0.13 auth module and using UPN logons fails authentication for all but User3.

I downloaded the modules from there.  Are they compatible with DNN 3.1?  

I followed your documentation and tried to set up the form authentication against LDAP and not very successful. I have some issues:

1. The userid that you have mentioned in the documentation what permission should it have to the AD information? should it have admin access?

2. What does the following  mean?

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Access all domains in the network:
Could not access LDAP to obtain domain entries

3. I have a news feed module on my home page which gets the feed from another module in my website.  When I turn on the windows authentication I get the following error on the feed: News Feed Is Not Available At This Time. Error message:Too many automatic redirections attempted.  How to correct this?

Early response appreciated.