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/21/2010 11:40 AM
 

I'll have to do some checking under a Windows authenticaiton setup in the web.config but..... the basic idea behind the provider from day one, as I understand it, was to give the option for users to be able to use their windows credentials to login to DNN under Forms authentication. Once you switch to Windows authentication you're basically taking the provider out of the equation. I have a feeling that if you disabled the provider everything would still work the same in on your website.

That said, I do know that under Forms authentication, if a user logs out it won't automatically log them back in again. Part of this is by design (it may be necessary to log out and log back in as another user) and part of it is IIS itself (under authentication it creates a temporary cookie that lasts anywhere from 30 minutes to an hour that needs to expire before authentication takes place again).

 
New Post
2/22/2010 3:09 AM
 

Hi Mike,

here's what I found out over the weekend.

- Under Admin/Extensions I have the Default Authentication Provider disabled and the ActiveDirectory Provider enabled.

- web.config is unchanged

- For the AD Provider, I had checked the "Hide Login Controls" option at the time I wrote my first post. I have now changed that to enable the AD Login control.

Now the portal behaves a bit more the way I want it to. After logout, the user is presented with the AD login screen and he can re-login using his AD credentials. Not exactly the way I want it, but better than before.

I still do not understand, why DNN in that case asks for Windows credentials at all. The user is already logged into the Windows domain, as this is an Intranet only situation. And the strange thing is that the first visit to the portal in the morning leads to an automatic login, just the way I'd want it to be. If the authentication cookie expires due to inactivity, the portal should simply renew that login.

But I guess my users can live with the current setting.

Klaus

 
New Post
2/23/2010 6:26 PM
 

Are your users still getting randomly logged out and then have to manually login? Or do they only have to login if they click the Logout button?

If it's the former I'll have to do some testing to refresh my memory on what happens (it's been a while that I just left a portal sitting there inactive) but I'm pretty sure on my portals it does automatically log the user back in.

If it's the later then it's as I said above, until the cookie expires it won't automatically log the user back in by design (the user clicked logout for a reason, generally to log in as another user).

 
New Post
2/25/2010 2:28 PM
 
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.
 
New Post
2/25/2010 2:33 PM
 
Klaus Holster wrote:

I still do not understand, why DNN in that case asks for Windows credentials at all. The user is already logged into the Windows domain, as this is an Intranet only situation. And the strange thing is that the first visit to the portal in the morning leads to an automatic login, just the way I'd want it to be. If the authentication cookie expires due to inactivity, the portal should simply renew that login.

If you are getting a Windows Authentication login, then DNN isn't asking for it, IIS is.  If the website is not listed (in the browser) as either an Intranet site or a Trusted site, IIS cannot automatically authenticate (unless you change the advanced settings), so it gives you the login prompt. 

 
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