Core Team, First off thank you for the new release, secondly THANK YOU for incorporating AD authentication into the core.

Now for my problems.

I had Tam's AD Provider 3.0.13 installed on my 3.1.1 instance and working fine.  When I extracted the files for the DNN 3.2 install overtop and ran the upgrade, origionally I recieved an error about a null reference (I think) on the authentication module and the install failed.  I had to comment out the section for Authentication in the web.config and then I looked at the new structure and realized the structure changed.  There Files DotNetNuke.Authentication.dll and DotNetNuke.Modules.Authentication.Admin.dll were not in the DNN 3.2 source, so I changed the extension to .old just to keep them there, then the install wen't successfull.  I also noticed that the Authentication directory under the DesktopModules directory was not in the source code as well so I moved that directory for the time being our of DesktopModules.

Once the system was running, I logged in with the host account to my portal and did not see any authentication options.  I then created a  chold portal and low and behold, authentication appeared in child portal under the Admin menu, however it does not appear in the initial primary portal?  Also, when I clicked on the authentication it shows a page with no modules and the title ..:: Admin >> Authentication ::..  ? Just out of curiosity I tried to add the Authentication module to this page, as we had to do in the 3.0.13 module, however the modules caused an exception since the Authentication directory was moved earlier out of DesktopModules. I figured this module entry was left over from the old install.  Shouldn't the upgrade remove this?  I then uninstalled the module and since a couple of the new dll's have the same name as the old ones, It wiped out a couple of the dll's needed for authentication, which I had to restore from the zip file.

Now I am stuck with a blank authentication page and no way to define the authentication for AD!

Can someone comment on this as what we are supposed to do for upgrading existing sites that had the 3.0.13 module installed, or the interim compilation that Tam released to some testers that had a couple extra projects.  Also can you tell me what is missing from that Authentication page and how I can restore it?

Thanks,
Nathan

Nathan,

  I am in the same boat, I am trying to upgrade to 3.2 but have had TAM's Authentication module running in production on the 3.1 version.  I think the best way to go is to remove the Authentication all together so it is back to a more default installation of 3.1 before upgrading.

Here is the steps I took to remove (what I believe) is all references and files of the Authentication module.

NOTE: I had the Authentication SignIn module installed also so my instructions include the removal of that also
_______________________________________________________

REMOVE THE OLD AUTHENTICATION BEFORE UPGRADE
_______________________________________________________
1) Comment out all authentication lines:

<sectionGroup name="dotnetnuke">
 <!--section name="authentication" ...

<httpModules>
 <!--add name="Authentication" ...

 <dotnetnuke>
     <!-- ADSI Authentication Provider -->
    <!-- authentication defaultProvider="ADSIAuthenticationProvider"> ...

2) Delete all instances of Authentication module from your portals

3) Empty out your Recycling Bin in Admin

4) Delete the Auth Modules in Module Settings

 If 4 fails then delete them manually by:
 ---------------------------------------
 a) Deleting "Auth.." records from DesktopModules 
 b) Deleting "Auth.." records from ModuleDefinitions
 c) Delete dll from "bin" folder DotNetNuke.Authentication.ADSIProvider.dll
 d) Delete dll from "bin" folder DotNetNuke.Authentication.dll
 e) Delete folder "Authentication" from "DesktopModules"
 f) Delete folder "AuthenticationSignin" from "DesktopModules"

5) Deleting all the record settings in the ModuleSettings table releated to the Auth Module (they will all have the same ModuleID)

6) At this point you have virtually whiped out the old version of the Authentication and a normal upgrade should work.

7) After you upgrade then uncomment the commented out Auth.. line under <httpModules>.

8) After you do this you might get an error when trying to login because the Authentication Module is not configured. Try refreshing the home page to login and if that fails try using ?ctl=login - that is how I was able to login.

9) Now you will have a page under the Admin section called "Authentication" to configure your AD Settings.

Please post any corrections or suggestions to this upgrade procedure.

Follow these steps upgrade core Windows Authentication if you have implemented pervious version of TTT Authentication
(ignore step 2, 3 if you didn't install TTT Authentication Signin module)

1.      Logon as Host
2.      Go to Admin/Site Settings page and change Logon page back to default DNN logon page
3.      Go to Module Definitions page remove TTT Authentication Signin
4.      Remove TTT Authentication module
5.      Open Host Settings page, clear cache 

At this point we're ready to upgrade DNN to 3.2. 

6.      Unzip new DNN 3.2 package
7.      Rename release.config into Web.config and modified required configuration value (i.e database, objectQualifier, MachineDecryptionKey…) . DO NOT enable httpModule for Authentication at this time (keep it comments out) 
8.      Open your DotNetNuke site in web browser, to process DNN upgrade
9.      Open IIS Settings, change security setting Admin\Security\WindowsSignin.aspx depends on your Authentication type (the old DesktopModules\Authentication\Logon.aspx is changed to this file)
10.  Open ModuleSettings table change the value of  ProviderTypeName 
from   DotNetNuke.Authentication.ADSIProvider, DotNetNuke.Authentication.ADSIProvider
into   DotNetNuke.Security.Authentication.ADSIProvider, DotNetNuke.Authentication.ADSIProvider
or you could delete all records related to old Authentication settings.
11.  Logon as Admin, go to Admin/Authentication to re-configure Authentication settings (You might not need to change anything here since the old settings still valid)
12.  Open Web.config, remove the comment of Authentication httpmodule to enable Windows Authentication automatic logon.

 Now, core Windows Authentication is ready

<This is where I am stuck I get the error message: "The default authentication provider specified in web.config is not configured properly. Authentication settings are disabled." >

Logon as Host, go to Host Settings page, clear cache to completely remove old settings.
Refer my previous post for more info

Good luck

Tam

Tam,

THANK YOU! :)

It worked.  However, I didn't have to do step 10 as the settings in the module settings table was already set.
Also, thank you for encrypting the password in the ModuleSettings now as well.

And I had to manually remove the Module via the tables and files since I installed a compiled version from source code I got from you a little while ago that was
slightly different and caused errors while trying to remove.

This something that that should be included in the documentation for 3.2/4.0 that isn't released yet and in the new DNN 4.0 book.

Thanks.
Nathan

TAM, 

Thanks it works now - The step I was missing earlier was deleting the old values out of ModuleSettings.

One last issue:  Doesnt seem like the cookie is working.  Eventhough it autologins in just fine if I close the browser (without using LOGOUT) and open it back up I have to clear out the cookie before it will auto login in.  I checked and verfied the cookie got created and that it expired in like 2 months. I am getting this behavior on a child portal where the parent portal is not using the Authentication if that is any clue.

Any suggestions? 

Is there documentation somewhere to setup Windows Auth from a new install? When I go to the Authentication setup I recieve this error:

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
The specified domain either does not exist or could not be contacted



However, I know the domian exists and is working.
  

anubisfm wrote:

Is there documentation somewhere to setup Windows Auth from a new install? When I go to the Authentication setup I recieve this error: Accessing Global Catalog: OK Checking Root Domain: OK Accessing LDAP: FAIL Find all domains in network: Could not access LDAP to obtain domains info The specified domain either does not exist or could not be contacted However, I know the domian exists and is working.

your answer can be found at this post DELETED and at TAM's blog on the DNN site.
NOTE: Looks like the moderator combinded some issues.

Your link does not work :(

See here for more information: http://forums.asp.net/1109431/ShowPost.aspx

I tried all the steps above on a server  running Win2K, net framework 1.1 with the latest updates I get the following error when attempting to set up Windows Auth. using the Admin Authentication form. The error pop up as soon as I click update on the form.

Error: Windows Authentication is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry() at DotNetNuke.Security.Authentication.ADSIProvider.GetNetworkStatus() at DotNetNuke.Modules.Authentication.AuthenticationSettings.cmdAuthenticationUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

Help

I've redone this system many times over the last many-many hours, I've upgraded to both 3.2 and 4.0 several times each.  No matter what I do, I do NOT get an another option under the Admin menu called Authentication.   I've went through the procedures in this thread, doing each one "exactly" as listed, no success.  What am I doing wrong? 

Quoting a post from another thread...

Yay!  After several more hours of investigation, I think I finally have an answer as to why I don't have the Authentication option in the Admin menu. It goes back to the documentation for the 3.0.13 Authentication Module where it says: Add Authentication Module   Create a new page name Authentication Add Authentication Amin module to this new page   Access this module, change and save Authentication settings for your portal I had a page called Authentication, which was a hidden page.  The upgrade installed the authentication module to this page instead of creating a new page under the Admin menu.  I was unable to move it to where it is supposed to be, but at least it is working, and I don't have to restore the entire website to a pre-v4.0 state...

Tam,

If someone has already done the 3.2.2 upgrade and cannot go back to earlier version is there a way to get the AD Authentication to properly work under 3.2.2. I am in this exact situation. I have tried removing all of your former modules etc and recopy over the 3.2.2 upgrade, but still do not get the Authentication form under the Admin section, nor does the Authentication work. This is on an intranet, and therefore crucial to getting it back up & running. I guess anyone who had previously logged into the intranet was not affected, but any new people are.

Thanks in Advance for you help,

Gerry

 

 

 

Gerry

Have you followed all steps of the instruction I posted here

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/234/Default.aspx