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 ForumsAuthenticationAuthenticationActive directory authentication in a non domain web server on IIS 7Active directory authentication in a non domain web server on IIS 7
Previous
 
Next
New Post
7/12/2011 6:32 AM
 

Hello,

I have some issue using Active Directory Provider in a DNN 5 installation in which the web server is not a part of active directory domain (it is in DMZ). In have read the documentation, so I have done these steps:

 1-Configured the active directory provider in DNN admin menu -> Extenisions

In this case, when I update the settings, I got this error:

Error: 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.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

 

2-Modified web.config adding <identity impersonate=”true” userName=”domain\user” password=”password” /> .

In this case I have also created a local user (local in the web server!) with same username and same password of the domain user stored in active directory. I have also granted full access to the dnn5 directory and added it into IIS_USRS group. OK. Repeating step 1 I got the same error.

 

3-Set Integrated authentication of WindowsSignin.aspx in IIS7:

I cannot set this option in IIS7 to this file, I can only set it to the directory in which it is stored (desktopmodules\Authenticationservices\Activedirectory).

 

Can anyone help me?

Thanks

Eclipse79

 
New Post
7/12/2011 10:33 AM
 
The problem is that the user account you're using for impersonation doesn't have permissions to read the Active Directory. It doesn't matter if it's the same username/password as an AD user because the information is passed by Domain\Username not just by Username.

As far as your number three problem. In IIS if you switch to Content View and drill down to WindowsSignin.aspx, right-click on it, and switch back to the normal view you can set permissions on that file alone (or you can just type the path to WindowsSignin.aspx in the address box in IIS).
 
New Post
7/12/2011 12:31 PM
 
Mike Horton wrote:
The problem is that the user account you're using for impersonation doesn't have permissions to read the Active Directory. It doesn't matter if it's the same username/password as an AD user because the information is passed by Domain\Username not just by Username.
no, the issue is different... I am checking at the firewall and the web server does not tries to contact domain controller. Our domain name is xxxx.local, so I have set dc=xxxx, dc=local in active directory authentication provider Root Domain option, and xxxx.local in default domain. Then, in order to convert the domain name to ip, I have added a line into "hosts" file so that xxxx.local points at the correct lan ip address of our domain controller server, but I see no entries in our firewall logs...

As far as your number three problem. In IIS if you switch to Content View and drill down to WindowsSignin.aspx, right-click on it, and switch back to the normal view you can set permissions on that file alone (or you can just type the path to WindowsSignin.aspx in the address box in IIS).

Founded! :) many thanks

 
New Post
9/22/2011 12:29 PM
 
I am also having this exact problem as I am running IIS7 and trying to get AD authentication working on a webserver that is not part of the AD domain. Is this possible as at the moment I am getting the following error on the settings page:

Error: 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.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

I know for IIS7 I need to use impersonation, is it possible to impersonate a user on my AD domain controller if it is on a different domain?

Thanks.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive directory authentication in a non domain web server on IIS 7Active directory authentication in a non domain web server on IIS 7


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