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 ForumsAuthenticationAuthenticationAuthentication Failure - Help !!!!Authentication Failure - Help !!!!
Previous
 
Next
New Post
7/14/2008 11:17 AM
 

 


Hi everyone, I cant get AD authentication to work and feel Im about to go mad. 

I installed the AD Authentication module, put the settings in, and everything checked out ok (I did everything else as per the setup notes). When going to authenticate it falls flat on its face, error message "Login Failed, remember that Passwords are case sensitive"

Ive tried:
- Turning on impersonation, didnt work
- Turning of DNN authentication and using just Windows AD, didnt work. This also included folder/file permissions
- Password length is set to 6 in web.config, just incase it was an issue but most passwords are 7 characters in length
- Going to the WindowsSignin.aspx page directly on the server (generates an error which is below) and a client pc, no joy.

Information
----------------------------
- DotNetNuke 04.08.04
- ActiveDirectory 01.00.03
- Windows 2003 R2 Domain Controllers
- Internet Explorer 7

- We have a master domain root.local and a sub forest call venus.local.  When setting up the AD Root Domain field info I entered DC=venus,DC=local as the domain to go to, this is where all our users are setup. Does it matter that our usernames are stored in different sub OU's, eg. Marketing, Sales?

- If I try to logon actually on the server I get:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace: [NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName) +69
   DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticationLogon() +254
   DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e) +103
   System.Web.UI.Control.OnInit(EventArgs e) +99
   System.Web.UI.Page.OnInit(EventArgs e) +9
   System.Web.UI.Control.InitRecursive(Control namingContainer) +321
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834

 
- In the event log on the DNN server the following entry is logged:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date:  14/07/2008
Time:  14:56:39
User:  N/A
Computer: WEBINT1-VEHO
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 7/14/2008 2:56:39 PM
Event time (UTC): 7/14/2008 1:56:39 PM
Event ID: b714359719ed4548bcbc3900438bf6a3
Event sequence: 32
Event occurrence: 2
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/700492692/Root-1-128605167054332826
    Trust level: Full
    Application Virtual Path: /
    Application Path: D:\Inetpub\wwwroot\intranet\
    Machine name: WEBINT1-VEHO
 
Process information:
    Process ID: 2344
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Exception information:
    Exception type: NullReferenceException
    Exception message: Object reference not set to an instance of an object.
 
Request information:
    Request URL: http://192.168.50.254/desktopmodules/authenticationservices/activedirectory/windowssignin.aspx
    Request path: /desktopmodules/authenticationservices/activedirectory/windowssignin.aspx
    User host address: 192.168.50.254
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 1
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName)
   at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticationLogon()
   at DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e)
   at System.Web.UI.Control.OnInit(EventArgs e)
   at System.Web.UI.Page.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
 
 
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 
New Post
7/14/2008 12:06 PM
 

It looks like you need to use impersonation in your web.config as per the documentation. NETWORK SERVICE is a local computer account and most likely does not have permissions to pull the user info from the AD.

 
New Post
7/15/2008 11:55 AM
 

I tried that before but it didnt work. However Ive created a new AD user called ldap, gave it permissions to the ldap directory to read info. I then updated the web.config to use impersontation as you said.

Two strange things, if I go to to http://intranet/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.asp it appears to login (it does show who you are logged in as though? Not sure if that is a feature or not)... however when I go to the authentication module plugin where the settings are and update to use the new user I get the below.... Im not sure if it is working or not now ??

Accessing Global Catalog:
FAIL
Checking Root Domain:
FAIL
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
A more secure authentication method is required for this server.


Thank you

 
New Post
7/15/2008 12:00 PM
 

 

Just change the authentication type to secure and I now get....

Accessing Global Catalog:
OK
Checking Root Domain:
FAIL
Accessing LDAP:
OK
Find all domains in network:
2 Domain(s):
root.local (ROOT)
venus.local (VENUS)

I cant login using the login form and i get the below message if i go to signin.aspx page directly:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName) +69
   DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.SynchronizeRoles(String LoggedOnUserName, Int32 intUserID) +42
   DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticationLogon() +234
   DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e) +100
   System.Web.UI.Control.OnInit(EventArgs e) +99
   System.Web.UI.Page.OnInit(EventArgs e) +9
   System.Web.UI.Control.InitRecursive(Control namingContainer) +321
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834

 

 
New Post
7/15/2008 12:44 PM
 

The provider isn't able to pull the user information from the Active Directory so there's a log jam somewhere between the server and the domain controller. You could try a program called LDAPBrowser (http://www.ldapbrowser.com) to test with. I use it when I'm coding to verify that I'm pulling the right information in (and to see what information I should be able to pull in). It might help point us in the right direction.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAuthentication Failure - Help !!!!Authentication Failure - Help !!!!


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