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 problem loging in after logoutAD problem loging in after logout
Previous
 
Next
New Post
10/19/2009 3:36 PM
 

 Here's one to bend your noodle...I have AD installed on 5.1.4 and everything was working fine.  I wanted to see if I could remove the domain name from what was stored in the db so someone suggested checking the strip domain name in the Settings page of AD.

That didn't work, so I went to set everything back the way it was.  Problem is, if you log out, you can't log back in.  Except for me, and my test account.  I've had other people in the department go to the dnn site, and it logs them in no problem, automatically, which is what I want.  But if they hit log out and try to log back in, Hitting the Windows Login button, it won't log them in, and throws this in the Event Log:

AssemblyVersion: 5.1.4
PortalID: 0
PortalName: Cypress Web Portal
UserID: -1
UserName:
ActiveTabID: 39
ActiveTabName: Home
RawURL: /Login.aspx?ReturnUrl=%2fAdmin%2fExtensions.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://portal02/Login.aspx?ReturnUrl=%2fAdmin%2fExtensions.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 0848340f-e91c-4a92-99a1-5f954b6f6ec6
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath
StackTrace:
Message: 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.GetDomainByBIOSName(String Name) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetUserEntryByName(String Name) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)
Source:
Server Name: PORTAL02

 

this is all internal.  The biggest problem is, it was working FINE this morning.  And if No One could log in, that would be one thing, but I'm the only one it seems to like, I don't understand.  That and why the username is missing in this error message.

 

any advice?

 
New Post
10/19/2009 4:12 PM
 

I'm in the process with the latest version of cleaning up the error messages and hopefully getting better information from them.

Quick question though.... you mention you checked the Strip Domain Name from the settings? Where did you do that? In the database or did you make the section visible in the .ascx page? There is a section there that was hidden with the intention of making it live at some point but I've never figured out a decent way to handle things if an admin decides to revert back.

There is however a visible section on the 05.00.02 version where you can enter the default domain so I'm just wanting to verify what you did before trying to answer.

 
New Post
10/19/2009 5:40 PM
 

Yeah, I changed it to visible = true on the settings.ascx page

The weird thing is, if you type in the domain in All caps, it seems to be okay, but only in some cases.  We're using two domains, one is a child of the other.  my personal id is in all small as is the domain, but everyone else seems to have to sign in using caps in the domain.  Thought it might be because it's the admin of the site, but there are two others, and they have to have all caps.

 

 
New Post
10/21/2009 12:56 PM
 

I suspect, without looking at the code, there's a problem when it's trying to verify the username that may be case sensitive compared to their current username. I haven't adjusted any of that code in well over a year because, even though it was added, it was never implemented.

So, to try to solve the problem. How are users currently stored in DNN? By their Username or by Domain\Username? Or do you now have a mix of both?

 
New Post
10/22/2009 11:29 AM
 

 I've started with another version - 4.9 of dnn because of some incompatibility issues with some other stuff, but I'm coming up against the same issue.

User goes to the page, and it autologs them in.  I'm starting with a new db, so I made the domain strip change before anyone logged in.  They're all being stored as their username only, no domain.  Logging out and logging in, using the Windows Login button to enter the username and pass doesn't work.  Still getting the same error message (no username):

AssemblyVersion: 04.09.05
PortalID: 0
PortalName: My Website
UserID: -1
UserName:
ActiveTabID: 38
ActiveTabName: Home
RawURL: /Home/tabid/38/ctl/Login/Default.aspx?returnurl=%2fHome%2ftabid%2f38%2fDefault.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://portal03.sacnrm.local/Home/tabid/38/ctl/Login/Default.aspx?returnurl=%2fHome%2ftabid%2f38%2fDefault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; Trident/4.0; GTB6; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 38d23cbb-9060-49c8-8f98-ffc9b5dafa35
InnerException: Logon failure: unknown user name or bad password.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DirectoryServices.DirectoryEntry.Bind
StackTrace:
Message: System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_NativeObject() at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.IsAuthenticated(String Path, String UserName, String Password)
Source:
Server Name: PORTAL03

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD problem loging in after logoutAD problem loging in after logout


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