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 ForumsAuthenticationAuthenticationActive Directory Provider for DNN 5Active Directory Provider for DNN 5
Previous
 
Next
New Post
2/25/2010 3:34 PM
 
Dan Ball wrote:
It's definitely cookie related. I just ran a test and upon clicking the logout button it will not do an automatic relogin, even if I restart the browser, until I remove the cookie. I cannot tell what the timeout is (cookie is all in code), so will have to run some tests to see if is expires in a few minutes or not.
 

It is indeed a 60 minute timeout before the cookie expires, which is the default setting defined in the web.config file...

    [authentication mode="Forms"]
      [forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" /]
    [/authentication]

I tested it and after 60 minutes it automatically logged me back in, even with the browser open.  So, it definitely is the cookie settings that are prohibiting the auto-relogin.

 

 
New Post
3/17/2010 4:27 PM
 

Is there documentation somewhere for this Extension?

 
New Post
4/20/2010 7:08 AM
 

I think I may have found the cause of the problem where users aren't automatically logged back in when their authentication cookie expires...

When a user logs in (either through DNN standard, windows manual or windowssignin.aspx) a cookie called ".DOTNETNUKE" is placed on their computer which is valid for the period specified in the web.config (default 60 minutes).

When a user is sent to windowssignin.aspx (either automatically by the authentication httpmodule or via a direct link) their windows credentials are requested and a cookie called "authentication.status.0" (0 since we are using portal ID=0) is written with a fixed timeout of one hour (AuthenticationController.vb line 535). Whilst this cookie exists the authentication module won't re-check windows credentials.

Now... why have we been having issues??? - I suppose there is a chance that some how the .DOTNETNUKE cookie is expiring before the authentication.status cookie, causing the user not to be logged in, but since the authentication.status cookie is still present their details aren't being re-checked.

Resolution.... I have set the timeout of the .DOTNETNUKE cookie to 61 minutes, so DNN should re-check windows credentials and update the .DOTNETNUKE cookie before the .DOTNETNUKE cookie expires, hopefully meaning we never have a situation where the sure is not logged in.

 
New Post
5/4/2010 3:41 PM
 
rvin2 wrote:

Quote:
Mike Horton wrote
 

rvin2, are you putting the Domain name in front of your user names (if you haven't setup the default domain in the settings)? How long is your password. By default DNN expects it to be 7 characters long. You can change this in the web.config if your password length is shorter.

Yes, I also tried with or without domain name as everytime I tried to set the default domain in the settings page it doesn't seem to save the value. When i update the settings it gives me a successful message but when i return to the settings page the default domain is blank.

Password lenght is not a problem. Other asp.net applications with AD authentication in the same server have no issues.

Is there any other way to troublehsoot this issue? thanks again!

It seems that part of this thread fell off somewhere.  But rvin2 mentions that the default domain goes blank when the page is refreshed.  I'm having that same issue.  If I don't include the default domain, I can login fine.  And when I put the default domain in, I can't login at all, until I refresh that page and the default domain goes blank again.

I just downloaded DNN 5.4.1 today, and included was AD 5.0.2 so I'm running the latest versions.  Any ideas?  Where's that value stored and maybe I can go check to see if it's actually being written where it's supposed to.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory Provider for DNN 5Active Directory Provider for DNN 5


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