Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationConfirmed and improved: AD Intranet autologinConfirmed and improved: AD Intranet autologin
Previous
 
Next
New Post
11/10/2006 10:03 AM
 

Joined: 1/1/0001
Posts: 0

Similar to my previous thread, I am confirming the following functions:

Objectives:

  1. Intranet site for corporate users
  2. All users are automatically logged in as the Windows user
  3. Security Roles named the same as AD groups will be updated automatically with User memberships
  4. No access to unauthenticated users (e.g. visiting vendors)
  5. Page access control using Security Roles (matched to AD groups)
  6. Simple base URL (e.g. "myhome") to access the site

I started with the following configuration

  1. W2K3 SP1
  2. .Net 2.0 plus all security patches
  3. SQL Server 2005 Express
  4. DNN 4.3.5 installed from Install.zip in C:\Inetpub\wwwroot\DotNetNuke 4.3.5
  5. "myhome" added as DNS alias for actual server name (e.g. "myserver")

I made the following modifications:

  1. Installed DNN AD Fix for DNN 4.3.5 from http://dnn.gmss.org
    1. Made a backup copy of the DLL's just in case.
  2. Changed Windows folder permissions
    1. Copied permissions from parent folder
    2. Added MYSERVER\NETWORK SERVICE with Modify permissions
  3. In IIS Manager:
    1. Under Web Service Extensions, made sure ASP.NET 2.0 was Allowed
    2. Added new Web Site called DotNetNuke 4.3.5 pointing to C:\Inetpub\wwwroot\DotNetNuke 4.3.5 using all other defaults
    3. Opened Propertied for Web Site DotNetNuke 4.3.5
    4. Under Web Site tab, Advanced... button, added "myhome" to host header value (since I am using a virtual server differentiated by a DNS alias)
    5. Under Home Directory tab, changed Execute permissions to Scripts and Executables
    6. Under Directory Security tab, Authentication and access control, Edit, removed anonymous access, ensured Integrated Windows authentication was checked.
    7. Under ASP.NET tab, ensured version 2.0 was selected (I didn't have any other versions installed anyway)
  4. Edited .\web.config file
    1. Uncommented the following line:
      1. <add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" />

I believe these are all the steps required.  Windows users should be automatically logged in when they enter http://myhome in their browser.

I also made a couple of cosmetic changes.

First, create a new page with the Hidden attribute selected.  On this page, add the Account Login module and a Links module.  To the Links module, add a link to http://myhome/admin/security/Logoff.aspx.  This is to ensure that you have a way to logoff as the current user and log back in as the Admin or Host user (or your regular user again).  I also added a link to http://myhome/admin/security/WindowsSignIn.aspx so I can easily log back in as my windows user.

In Site Settings, Advanced Settings, Security Settings, I changed User registration to none since I do not want users to attempt to register.

In order to prevent users from logging off, I then modified the file C:\Inetpub\DotNetNuke 4.3.5\Portals\_default\Skins\DNN-Blue\Horizontal Menu - Fixed Width.ascx as follows:

<TD width="200" vAlign="top" align="right" nowrap><dnn:USER runat="server" id="dnnUSER" /><!--&nbsp;&nbsp;<dnn:LOGIN runat="server" id="dnnLOGIN" />--></TD>

I know this is a long post, but I wanted to put everything in one place.

I would would really like to know if anyone can reproduce the behavior I describe on their own and confirm these steps.
 
New Post
11/10/2006 10:56 AM
 

Joined: 1/1/0001
Posts: 0

I already have an update after more testing.  Incidentally, I confirmed that I have the 11/9/2006 version of Mike Horton's AD fixes (based on Stuart Hilbert's fixed for 3.3.5) from the link in the above post.

Here are the things I tested:

  1. If a user's AD group membership changes, are the Security Roles refreshed when the user logs in again?  For example:
    1. I have an AD Group called Accounting with a matching DNN Security Role called Accounting.
    2. I have an AD Group called Operations with a matching DNN Security Role called Operations
    3. I have an AD User, Bob, who a member of the AD Accounting group.
    4. Bob visits DNN for the first time, and DNN creates an account for Bob (since I am using autologin as above) and adds Bob to the DNN Security Role Accounting
    5. I now remove Bob from the AD Group Accounting and add him to the AD Group Operations
    6. Bob visits DNN again, and DNN removes hime from the DNN Security Role Accounting and adds hime to Operations.
  2. If the AD group contains nested groups, will users who are members of the nested groups be recognized as members of the parent group?  FOr example:
    1. The AD Group Accounting above contains AD groups Accounting Managers and Accounting Staff, which in turn contain Users.
    2. DNN has a Security Role Accounting.
    3. Mary is a member of the AD Group Accounting Staff.
    4. Mary visits DNN for the first time, and DNN creates an account for her and adds her to the Security Role Accounting.

My testing shows that both 1 and 2 fail.

Regarding (1), I can delete the user account in DNN, visit DNN again, and the roles are correct.  However, (2) does not work at all.

Please correct me, but I thought the Mike's fix addressed (1).
 
 Page 1 of 1
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationConfirmed and improved: AD Intranet autologinConfirmed and improved: AD Intranet autologin


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out