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 ForumsAuthenticationAuthenticationAnonymously authentication only works after browser is closed then reopenedAnonymously authentication only works after browser is closed then reopened
Previous
 
Next
New Post
8/6/2012 3:35 PM
 

DNN Version: 6.1.5

I have two DNN sites that were developed as separate websites and were working 100% flawlessly. Both sites use mixed mode authentication and allow DNN or AD login. Both sites allow anonymous access so logging in is optional.

However, in order to get my SSL cert to work, I had to make one site a Virtual Directory of the other. Now, every time anyone navigates to the virtual directory, a windows box pops up asking for AD username/password. If you cancel the box, an authentication failure message is displayed (as expected). BUT, if you close the browser and re-open it, anonymous mode kicks in (as configured) and the home page pops up without asking for a username/password.

Why in the world is the login box popping up the first time, then on closure and reopening of the browser, anonymous access starts working? I have given the NETWORK SERVICE account full permissions to the directory (including WindowsSignIn.aspx), which is used as the app pool identity.The root site is still working perfectly and does not ask for credentials.

I have tried accessing the site from more than 5 computers including firefox and IE9. Any guidance would be appreciated!

Thanks,
Robert

 
New Post
8/8/2012 12:39 PM
 

I finally figured out the issue!

After converting the secondary site to a virtual directory, I had to place a bunch of <remove name=""> tags in the web.config file to stop inheritance. I overlooked one of the authentication tags that should have been removed (via tag) as well! One I added the <remove> tag, the site began working perfectly.

Robert

 
New Post
8/8/2012 1:16 PM
 
Glad you got this figured out Bobby. Could you document exactly what you did and then send it to me? I'd like to add it to the documentation.
 
New Post
8/8/2012 3:55 PM
 

Hi Mike,

Certainly!

The line below in bold was missing... because it wasn't throwing an error, I didn't <remove> it. So the virtual directory was trying to inherit the Active Directory authentication from the root site.

Here are all the <remove> tags that I added to the site's web.config file, to get the site to function properly as a virtual directory. It appears dotnetnuke 6.1.5 automatically created the site aliases, but I would recommend adding them manually before moving the site.

<connectionStrings>
   <remove name="SiteSqlServer" />

<system.webServer>
    <modules>

      <remove name="ScriptModule" />
      <remove name="Compression" />
      <remove name="RequestFilter" />
      <remove name="UrlRewrite" />
      <remove name="Exception" />
      <remove name="UsersOnline" />
      <remove name="DNNMembership" />
      <remove name="Personalization" />
      <remove name="Analytics" />
      <remove name="ClientDependencyModule" />
      <remove name="MobileRedirect" />
      <remove name="RadUploadModule" />
      <remove name="FormsAuthentication" />
      <remove name="Authentication" />
......

<handlers>
      <remove name="WebServiceHandlerFactory-Integrated" />
      <remove name="LogoffHandler*" />
      <remove name="RSSHandler" />
      <remove name="LinkClickHandler" />
      <remove name="CaptchaHandler" />
      <remove name="ScriptHandlerFactory" />
      <remove name="ScriptHandlerFactoryAppServices" />
      <remove name="ScriptResource" />
      <remove name="UserProfilePageHandler" />
      <remove name="RadProgressHandler" />
      <remove name="ClientDependencyHandler" />
      <remove name="Telerik.Web.UI.WebResource" />
      <remove name="Telerik.Web.UI.ChartHttpHandler" />
      <remove name="SitemapHandler" />
      <remove name="HtmTemplateFileHandler" />

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAnonymously authentication only works after browser is closed then reopenedAnonymously authentication only works after browser is closed then reopened


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