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 Authentication only logs some user in, not allAD Authentication only logs some user in, not all
Previous
 
Next
New Post
11/4/2010 12:49 PM
 
It has been a while since I've worked on my client's intranet site but they are wanting to go live soon and we've discovered that some users get logged in when they browse to the site from any other machine onthe network and others do not.  Other than something I missed while setting up AD Authentication, there is one item that could be responsible, but I need some DNN team feedback to help me downthe right troubleshooting path.

The AD Authentication extension only creates a user when they first visit the site.  This is fine unless you have 1000 users that all need to be configured in various roles before the launch of the site - i.e. I can't wait for them to visit the site.  So, I used a 3rd party AD import tool and it pulled all users from AD.  This seemed to work just fine except that now I'm discovering that the few users I created manually get logged in just fine using Windows authentication but the users imported do not. 

My question is...how does the AD Auth extension validate a user?  Does it only got to AD if the user does not exist?  I notice that the import tool did not set the Create Date field in the user record - would this cause a problem?

Any informatin would be greatly appreciated.  I can't aford to delete all the users for the roles reaon mentioned above.
 
New Post
11/4/2010 1:22 PM
 
The provider checks against the AD every time a user logs in. If they log in automatically then it checks to make sure they're a valid AD user on the domain and if they log in manually then it checks to makes sure they've entered a valid password. If you have role synching turned on then it also has to make sure the roles are correct but, regardless, it checks against the AD every time.

Without testing against the import tool you used I can't give you a definitive answer but based on it working on manually created users and not imported users then I lean towards blaming the import tool. The first thing I'd try is adding a created date to one of the users and then testing that user. It may be something as simple as that. You could also try manually logging in with the imported user and seeing if any of their records in the database change. The only other thing I can think of is that the import tool is missing a critical step on the import or is perhaps meant for an older version of DNN.

With the AD provider, for general login, all it really does is authenticate against the AD and passes that information on to the DNN user controls. I.E BobS logins in with his AD account so his credentials are checked against the AD. They pass so then it uses the DNN procedures to see if the user exists in the portal. If it doesn't then it passes the required information to the DNN code that creates a user which is the same code that's used on a standard user registration. If the user does exist then it logs the user into the portal using the same procedures that are used for a standard login.
 
New Post
11/4/2010 1:45 PM
 
Mike,
I tried deleting my test user and then accessing the intranet site from a machine where I was logged in as that user. The problem seems to be something fundamental. When I 1st browse to the site I get an error - the second time I get in to the site but I am not logged in - I am just at the home page wityh the typical Login link. Am I missing something simple? Below is the error:

Server Error in '/Intranet' 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.AuthenticationController.AuthenticationLogon() +376
DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e) +127
System.Web.UI.Control.OnInit(EventArgs e) +131
System.Web.UI.Page.OnInit(EventArgs e) +15
System.Web.UI.Control.InitRecursive(Control namingContainer) +142
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1476
 
New Post
11/4/2010 1:47 PM
 
Another issue I'm seeing, and I hope it's ok to address it here....is that all my user names are preceded with the domain name, which happens to begin with a #. 6Mpreddy, 6Mmvanerik, etc...

Becasue of this I can'tuser the user management UI to find users - it only allows me to search by letter!
 
New Post
11/4/2010 2:28 PM
 

Hey Mike,

One more update before I head out for the day.  I went ahead and deleted all users that were created via the import and reseeded the users table ID.  I'm seeing varying results now with my testing.

I first logged in to my machine as user A, browsed to the site, and viola - it worked! - logged me in just fine.

I then logged in as user B, browsed to the site, but did not get logged in.  No errors & nothing in the event log indicating that any attempt was made to authenticate against AD.

I then followed the Login link and logged in manually - worked fine - authenticated against AD and created the user.

I then deleted both users again and ran the test again.  This time neither user was logged in/authenticated against AD automatically, but again, when I logged in manually it did authenticate and create the users.

Do you know why it doesn’t always authenticate against AD went the user browse to the site?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Authentication only logs some user in, not allAD Authentication only logs some user in, not all


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