DotNetNuke and Windows Authentication

I hadn't worked with DotNetNuke and Windows Authentication at all, but last week a client came to me and wanted a portal setup that works with their Active Directory for logins. I ended up using the TTTCompany Windows Authentication module. It worked perfectly, done and setup in roughly 3-4 hours, but it could have been done in half the time, I also installed the PA version of the TTTCompany Application pack for the client so that they have an image gallery to use.

The level of work on the DNN project has been great, and the support from the forums is top-notch as well. If you haven't checked out DNN and need a portal application check it out, I mean, even I developed a module for it!

[Now Playing: Megadeth - Five Magics ]

14 Comments

  • How did ya do it..?

    I used the TTTCompany code... but it doesn't seem to work properly.

    Probably me, though.



    What took all the hours to make it work..?



    THanks...





    Ivo

  • Well, most of the time it took me to set it up was time spent testing, once I had the correct information (AD administrator account/pw) then it was pretty much set it up and go.

  • How are you using windows security groups in DNN? I to use windows authentication and can't get DNN to recognize windows groups as security roles in DNN

  • I setup admin roles, and then the client I set everything up for did the rest of the administration of their groups.



    Are you getting any of the windows authentication to work?

  • Hi,

    Thanks for posting the link to TTT. This looks like a great package. I'm trying to install now, but I have a question about one of the steps in the implementation section of the manual. How do I "Add reference System.DirectoryServices.dll & TTT.DotNetNuke.DirectoryServices.xxx.dll". I also don't understand "Include \controls\ASDIControl.aspx(.vb) into your project". I assume I have to do this in Visual Studio, but I'm not sure. Any help would be appreciated.

  • Jim, you are correct, you will need to do all of this in visual studio. Once you have the DotNetNuke project in Visual studio you can right click on the references folder and point to the above DLL.



    You'll also have to add the controls file to your project. Rebuild the project and then move it onto your production server.

  • sweet - i'm enduring the long install process now... i'll post again when there is some progress or problems. =)

  • note to world: you must install vs.net 2003, NOT vs.net. ugh.... talk to you again in about 2 hours...

  • done! rebuilt without a hitch. i think the docs should go into a bit more detail about how to add the references and control (for us who are new to vs.net) but i figured it out pretty quickly.

  • I used vb.net 2003 to add reference to the two dll's and included the adsicontrol. I just drug those into the controls folder. I don't know if that is exactly how you are suppost to do it. I saved the project and then rebuilt it. It said it rebuilt without any errors but I still get the following when trying to access the home page:



    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.



    Parser Error Message: Access is denied: 'TTT.DotNetNuke.DirectoryServices.2.0.3'.



    Source Error:





    Line 256: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

    Line 257: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

    Line 258: <add assembly="*"/>

    Line 259: </assemblies>

    Line 260:





    Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 258



    Assembly Load Trace: The following information can be helpful to determine why the assembly 'TTT.DotNetNuke.DirectoryServices.2.0.3' could not be loaded.





    === Pre-bind state information ===

    LOG: DisplayName = TTT.DotNetNuke.DirectoryServices.2.0.3

    (Partial)

    LOG: Appbase = file:///C:/DotNetNuke

    LOG: Initial PrivatePath = bin

    Calling assembly : (Unknown).

    ===



    LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

    LOG: Post-policy reference: TTT.DotNetNuke.DirectoryServices.2.0.3

    LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dotnetnuke/1d8ef227/82181fa7/TTT.DotNetNuke.DirectoryServices.2.0.3.DLL.

    LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/dotnetnuke/1d8ef227/82181fa7/TTT.DotNetNuke.DirectoryServices.2.0.3/TTT.DotNetNuke.DirectoryServices.2.0.3.DLL.

    LOG: Attempting download of new URL file:///C:/DotNetNuke/bin/TTT.DotNetNuke.DirectoryServices.2.0.3.DLL.









    --------------------------------------------------------------------------------

    Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

  • Scratch that. The permissions on the dll was wrong for some reason. I got in now but when I hit the login button it says and error has occured. Error loading module.

  • TTTCompany Windows Authentication module. link is broken. Do you have a copy of the module I could use?

  • I'm using the module to authenticate Intranet users. I've got a bit of a weird problem though... Some users get prompted to enter their Windows logon whilst others don't. Bizarrely, it only seems to be the admin users who see the prompt whilst all standard users get authenticated with no prompt.



    Taking a look at the logs there seems to be some images that return a 401 status. For example:



    2004-07-22 08:50:07 192.168.x.x - 192.168.x.x 80 GET /Images/spacer.gif - 401 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0;+.NET+CLR+1.0.3705;+.NET+CLR+1.1.4322)



    If the user simply clicks OK and does not enter any logon details then the portal is displayed regardless. I've tried setting the images folder to allow anonymous access but that doesn't solve the problem.



    My settings are as follows:



    Environment : Windows 2000 server without Active Directory



    ADSI settings : Authentication Type = None



    IIS settings : Integrated Windows Authentication = checked (all other authentication methods unchekced)



    Any ideas what could be causing this?

  • Solved the problem...soon as I setup a DNS record it solved itself. Guess its probably down to it being a non trusted site. Also noticed that if I added the IP address to Intranet zones in IE settings there was no problem. Weird though how it seemed to work for some people and not others...

Comments have been disabled for this content.