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 ForumsAuthenticationAuthenticationDNN 6.2, AD 5.0.4 & autologinDNN 6.2, AD 5.0.4 & autologin
Previous
 
Next
New Post
6/21/2012 12:35 AM
 
I'm in the process of testing an upgrade to DNN 6.2 and also the AD Provider 5.0.4.Once I upgrade to 6.2 the autologin no longer works. It is as though the AD httpmodule is not being loaded at all. When a user visits a portal that requires authentication, they are redirected to the normal login page & not the windowssignin.aspx

Is anyone else having this problem?

A possible work around for us is to make it so that our standard login page redirects to the windowssignin page, but this means that the page the user was trying to access is lost and they are redirected to the home page.

Cheers Wayne

BTW - A side effect of this is that it does eliminate the 302 redirect loop for search engine bots that happens when using the AD provider on sites available to the public.

This is also posted in the community exchange @ http://www.dotnetnuke.com/Community/Community-Exchange/Question/1129/DNN-6-2-AD-Provider-5-0-4-autologin.aspx

 
New Post
6/21/2012 10:08 AM
 

Hello,

I have the same problem as you. If i tried to access to windowsSignin.aspx, i'm logged in with my windows account but the httpmodule doesn't seems to redirect any user to this page.

If I enable windows authentication on the website level, I'm directly logon but i cannot login with the standard host account (the deconnexion works but not the connection).

I tried on a new dnn6.2 install on a IIS6 server and then on a IIS7(integrated or classic app pool) without any difference.

Is there any problem with the HttpModule?


Jean-Baptiste Bouillet
Developer - Aricie
 
New Post
6/21/2012 10:37 AM
 
I checked one of my instances of DNN 6.2 (Server 2003) and I cannot duplicate the problem you both are seeing. I will have to test on my internal install at home running on Server 2008 R2 when I get home. I haven't updated that one to DNN 6.2 yet but in my testing on the betas in my development system i don't remember any issues (or I would've fixed them or had fixes in the pipeline already).
 
New Post
6/21/2012 10:58 AM
 
Thanks for your feedback.
The only way for me to be autologin is to enable windows activation and disable form authentication on entire website. If I do that, i cannot logoff anymore to switch to a host account. (I have older websites on dnn4.9,5.2 and the ad provider work correctly). It seems I used the same configuration :
Authentication settings:
Enabled=true
Provider=ADSI
Authentication type=delegation
Email domain=@mydomain.com
That's the only field I configured and since it work when I access on the windowssignin.aspx page, i think it should be ok.
The only problem for me is the httpmodule which doesn't redirect but maybe i missed something else.

Jean-Baptiste Bouillet
Developer - Aricie
 
New Post
6/21/2012 6:59 PM
 
As always thanks for looking into this Mike.

I forgot to mention that our environment is Win 2008R2, .NET 4 & integrated pipeline.

I tried a couple of times tp reset our test/staging environment & then perform the upgrades, but get the same result.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationDNN 6.2, AD 5.0.4 & autologinDNN 6.2, AD 5.0.4 & autologin


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