Products

Solutions

Resources

Partners

Community

Blog

About

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 ForumsAuthenticationAuthenticationAD/IE NTLM AutologinAD/IE NTLM Autologin
Previous
 
Next
New Post
3/8/2011 11:40 AM
 
Mike Horton wrote:
Ah sorry, my bad on the R2/SP-2. I've had it running on regular 2008 in the past as well.

My initial reaction is that you should try impersonation but you say it is working when you login manually. Is that the case for new users as well? 90% of the time the majority of errors are fixed if impersonation is used.

 
I removed everything again (including domain users, DNN security groups, etc) and reinstalled the module.  Setup the AD module as per the documentation and still no go.  Can and does successfully log into the DNN using my DNN credentials.

If I look at the Domain Users DNN group, I see that my domain account is listed here and it also has my Domain information automatically entered.

Not sure why this is happening nor what I can do to fix this.

 
New Post
3/8/2011 12:48 PM
 
In chapter 3 step o, it describes steps needed for impersonation.  I tried this but it caused the site to crash; so I had to remove this line.

My Authentication mode within my web.config file is configured for "Forms".

I have no issues with logging in using my AD credentials manually, nor do I have issues when Update the settings of the AD Provider.  Its sees the LDAP, the domain root and the 6 sub-domains.

I'm using AD authentication for our intranet site.  It's a child portal of our main live site which allows for anonymous access.  We want our users to be able to use their domain credentials to view the intranet site from externally to our network.
 
New Post
3/8/2011 1:02 PM
 
So if you uncomment in your web.config you get the trust error but if you login manually it works correct?
 
New Post
3/8/2011 1:17 PM
 
Mike Horton wrote:
So if you uncomment in your web.config you get the trust error but if you login manually it works correct?

 If I uncomment the "<add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />" line, I get the "The Active Directory Provider requires the site to be running under Full Trust and/or in Classic mode in IIS 7.0" error when I hit any page on our site.

If I try to impersonate as per the instructions in Chapter 3, step O, I get another error: "Parser Error Message: Unrecognized element 'identity'."

Plus, I still get the error on the bottom of Page 1 (http://www.dotnetnuke.com/Resources/F...)  which Richard talks of as well as Doug on page 4 (http://www.dotnetnuke.com/Resources/F...).

I'm totally lost and have tried everything I can think of to get this to work.  I know it worked properly with Server 2003/IIS6, so it's obviously a Server 2008/IIS7 configuration issue.  But what that is, I haven't a clue.

I have the site running under it's own AppPool which is setup for Classic and it's identity is running as Network Service.

 
New Post
3/8/2011 1:38 PM
 
Jeff Maze wrote:
Mike Horton wrote:
So if you uncomment in your web.config you get the trust error but if you login manually it works correct?

 If I uncomment the "" line, I get the "The Active Directory Provider requires the site to be running under Full Trust and/or in Classic mode in IIS 7.0" error when I hit any page on our site.

If I try to impersonate as per the instructions in Chapter 3, step O, I get another error: "Parser Error Message: Unrecognized element 'identity'."

Plus, I still get the error on the bottom of Page 1 (http://www.dotnetnuke.com/Resources/F...)  which Richard talks of as well as Doug on page 4 (http://www.dotnetnuke.com/Resources/F...).

I'm totally lost and have tried everything I can think of to get this to work.  I know it worked properly with Server 2003/IIS6, so it's obviously a Server 2008/IIS7 configuration issue.  But what that is, I haven't a clue.

I have the site running under it's own AppPool which is setup for Classic and it's identity is running as Network Service.

 Hello.. I think I figured something out which works.

For the AppPool of the website, if I set this up to use a domain user, I no longer get the configuration error as previously described; screen from of Richard's in his thread.

If I uncomment the "<add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />" line, I get a request for permissions pop-up instead of the standard login type screen.  So I've left this line commented out so I can use the login screen.

Auto-login doesn't appear to work properly, but am not sure where to look for this.  When it was on the internal development box, I'd hit the site and it'd use my NTLM credentials (IE8 and Chrome seemed to work) and log me into the site automatically.

Hope this helps..

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD/IE NTLM AutologinAD/IE NTLM 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