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 ForumsAuthenticationAuthenticationDisplayName instead of FirstName???DisplayName instead of FirstName???
Previous
 
Next
New Post
8/30/2006 2:39 PM
 

Sorry about cross-posting, but I noticed the same thing when I installed AD for 4.3.4. The problem has to be with DNN. I wrote scripts in classic ASP that were able to extract the FirstName and LastName from the domain controllers which work ok. But not in DNN 4.3.4.

I installed a copy of DNN 4.03 and the AD worked ok. FirstName, LastName and Username can be extracted in 4.03 but not in 4.3.4. There is a problem with this module in 4.3.4.

 
New Post
8/30/2006 11:41 PM
 
catsnak wrote

Lev,

Thanks for the info. I downloaded the LDAP browser and we were able to access AD. So I atleast know now that the server running DNN can access AD and we were able to verify that the givenName and sn fields were there and filled in properly. This leads me to believe that your first scenario is the problem and for some reason DNN itself can't access AD. Any ideas on what could be causing this and how to fix it? I'm also still getting the error that windows authentication is unavailable when ever I try to set it up through DNN and we've tried everything. Right now it's in a partial working state even though DNN says it's not available, users are getting auto logged in but we have to go into the database and fill in the name information. We also have another odd issue where one user keeps getting logged in as the server admin instead of himself. I'm starting to think somewhere along the line I borked something even though this is a fresh install and we haven't made any modifications to any of the code other then following the steps laid out here in the forums for trying to get windows auth working.

At this point I'm at a complete loss!

David

David,

I am not sure about what is going on. At this point I would have dived into DNN source code and actually debugged it through VS 2005 debugger. That way you can see excatly what's going on.

To do this get source code for DotNetNuke.Authentication.ADSIProvider (and possibly DotNetNuke.Authentication.ADSI too), compile them with debug symbols, then place into bin\ folder. Connect to the running DNN ASP.NET application with VS 2005 debugger using process attach (aspnet_wp.exe on IIS5 and w3wp.exe on IIS6), and try to set breakpoint on method "DotNetNuke.Security.Authentication.ADSIProvider.GetUser" (open the VB source file and set breakpoint).

If setting breakpoint this way fails, you can use an old trick. Modify source code for GetUser method to make first like System.Diagnostics.Debugger.Break(). Then application will break and ask for debugger to attach by itself.

Go through it line by line and see how it behaves behind the scenes, i.e. whether it actually connects to AD and whether AD connection information is correct in the program. That would be my approach, coming from a development background.

Hope this helps,

Lev.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationDisplayName instead of FirstName???DisplayName instead of FirstName???


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