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 ForumsAuthenticationAuthenticationProblem with AD authentication in DNN 4.8.2Problem with AD authentication in DNN 4.8.2
Previous
 
Next
New Post
5/13/2008 1:07 PM
 
Fernando Delfino

Joined: 4/25/2008
Posts: 1

Hi everyone,

I have a few problems with AD authentication. 

First I've tried to activate AD autentication (ADSIAuthenticationProvider and Delegation), Root domain DC=XXXX and User Name XXXX\YYYYY (this is a user with access to the domain) but the result was

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 changed the config to Root domain XXXX.COM and User Name XXX\YYY and the result was
Accessing Global Catalog:
FAIL
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password. 

So I start to google about AD Authentication but all the information about it was ralated to earlier versions of DNN.

I didn't give up, and make some changes to the web.config, switching the authentication mode from Form to Windows (including uncommenting the impersonate node) and the authentication became to work because it didn't ask me to log in altought it's not enabled from ADMIN > Authentication!!!!

I went to the Authentication option and turn it on and the initial settings from the post (ADSIAuthenticationProvider, Delegation, Root domain DC=XXXX and User Name XXXX\YYYYY) and the result was

 

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):
icebergsolutions.com (ICEBERGSOLUTION)

The problem is that I have 2 child portals (linked in the menu thru 2 pages in the parent portal using a Link to an external resource but pointing to the child) and when I click on one child, the status bar from the IE starts to flick, I cant view anything and after that I get a timeout error.

May be that's not the correct way to link to subportals, but I didn't find other one.

Other problem that I'm getting it's that 3 domain users were created automatically during some test, but now I tried to enter (to the parent portal) from another machine with other user logged in and I get the flicking in the status bar.

Do you have any idea about those problems?

Thanks,

Fernando

 

 Other notes about the web.config:

The line  <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" /> is uncommented and the line <!--add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / --> crearly commented
 
New Post
5/13/2008 5:34 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Fer wrote

Hi everyone,

I have a few problems with AD authentication. 

First I've tried to activate AD autentication (ADSIAuthenticationProvider and Delegation), Root domain DC=XXXX and User Name XXXX\YYYYY (this is a user with access to the domain) but the result was

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 changed the config to Root domain XXXX.COM and User Name XXX\YYY and the result was
Accessing Global Catalog:
FAIL
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password. 

So I start to google about AD Authentication but all the information about it was ralated to earlier versions of DNN.

I didn't give up, and make some changes to the web.config, switching the authentication mode from Form to Windows (including uncommenting the impersonate node) and the authentication became to work because it didn't ask me to log in altought it's not enabled from ADMIN > Authentication!!!!

That's because you're bypassing all authentication in DNN and using Windows period. You're not even hitting the AD code.

I went to the Authentication option and turn it on and the initial settings from the post (ADSIAuthenticationProvider, Delegation, Root domain DC=XXXX and User Name XXXX\YYYYY) and the result was

 

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):
icebergsolutions.com (ICEBERGSOLUTION)

The problem is that I have 2 child portals (linked in the menu thru 2 pages in the parent portal using a Link to an external resource but pointing to the child) and when I click on one child, the status bar from the IE starts to flick, I cant view anything and after that I get a timeout error.

May be that's not the correct way to link to subportals, but I didn't find other one.

Other problem that I'm getting it's that 3 domain users were created automatically during some test, but now I tried to enter (to the parent portal) from another machine with other user logged in and I get the flicking in the status bar.

Do you have any idea about those problems?

Thanks,

Fernando

 

 Other notes about the web.config:

The line   is uncommented and the line crearly commented

A couple of things: The error you were getting originally was because you need to uncomment the <impersonate="true" /> line from the web.config and only that line from that section (leave DNN using Forms authentication). You'll have to make some additional changes to it that are covered in the documentation.

The screen flashing that you're seeing is a side effect of changing the authentication in the web.config from Forms to Windows. If the account already exists in the DNN database the user is logged in but if it doesn't the application gets thrown into a loop. I posted some links in the last couple of weeks on some possible fixes for that and I'll see if I can find the post that they're in.

Child portals have been an issue with the AD provider for a long time but I think I've got it fixed in the 01.00.04 beta (see the pinned post at the top of the forum).
 
 Page 1 of 1
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationProblem with AD authentication in DNN 4.8.2Problem with AD authentication in DNN 4.8.2


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