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 ForumsAuthenticationAuthentication04.08.04 to 5.00.00 AD single signon not wotking04.08.04 to 5.00.00 AD single signon not wotking
Previous
 
Next
New Post
1/9/2009 8:06 AM
 

I had a fully working sight under 04.08.04 then I upgraded to 05.00.00 and now I cannot access the site single sign-on with AD. Using DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx displays a message 

 Well I have anonymous access turned off and integrated Windows authentication turned on. I even went as far as checking Digest authentication for Windows Domain server, still no luck. I also tried changing the web.config to windows authentication mode and it still says authentication is disabled, WTF guys? I restored to the old version from all the full backup's and guess what I am still not working, thank god this is a development environment.

Can anyone assists?<!-- forms or Windows authentication --><identity impersonate="true"/><authentication mode="Windows">authentication>

 

 

<authentication mode="forms">

<forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies" />

</authentication>

 

 

 

 

</

 
New Post
1/9/2009 12:28 PM
 

WHen you upgraded to 05.00.00 did you a) upgrade to the 05.00.00/05.00.01 version of the AD Provider (the 01.xx.xx versions will not work with DNN5) and b) did you enable the provider under Admin->Extensions->AD provider?

There was a major change in architecture from DNN 4 to DNN 5 and the settings for the provider are no longer stored in the ModuleSettings table but are now stored in the PortalSettings table (the reason why the 01.xx.xx versions won't work in DNN 5). That said, there is a bug in the 05.00.00 version but you can get a fixed version (05.00.01) from my website (http://dnn.gmss.org) until the .01 release makes it through the DNN Release Tracker.

Now, just to make sure I understand you correctly, when you restored back to 04.08.04 files/database you are still getting the same message? Have you cleared your Temporary .NET Files/restarted IIS/etc?

The only time under normal circumstances that you should see Windows Authentication Disabled message is if someone goes direct to WindowsSignin.aspx and the provider hasn't been enabled.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthentication04.08.04 to 5.00.00 AD single signon not wotking04.08.04 to 5.00.00 AD single signon not wotking


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