I have set ADSI settings including to use synchronization. Created an Sec Role in DNN matching an AD one. Changed web.config to windows auth and logged in as an AD user with membership in the matching Sec Role. Changed auth back to forms and logged in as Admin to verify user was created and populated in the matching group. OK---thus far.....successful....BUT.....

Changed back to windows auth and the same AD user trys to login and no error given, but not page change (still have login link at top vs. username and logout option).

I made sure I had created a new page in the portal that gave that AD / SecRole members view/edit rights. Even put the AD user in the DNN administrators Sec Role...........still no go.

If anyone can point out my obvious lack of knowledge in this matter I would be very grateful.

I had all ths working in 2.x using Tam's ADSI module including single signon........which brings me to another point....how do I enable single sign on in 4.0.2? Do I need some module, or have to edit core code?

Thanks in advance.

Figured it out. Was trying to include steps from previous versions and memory....bad combination.

Fresh install 4.0.2

Leave it in Forms Auth

Setup the ADSI connector and create the Sec Roles that match AD roles.

Log on as a user Domain\User and they get registered and show in matching groups / Sec Roles.

2 Hurdles left.....setting default domain to Domain\User doesn't have to be used and how to implement single signon for intranet apps.

Any help most appreciated.