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 authentication on multiple DNN instancesActive Directory authentication on multiple DNN instances
Previous
 
Next
New Post
2/18/2011 2:29 PM
 
Environment:
OS: Windows Server 2008R2 with IIS7.5
DNN:  5.06.01
DB: MS SQL Server Express

Our current DNN instance (4.08.04) is installed on a different server (Win Sever 2003) than the environment listed above.  I am using Active Directory authentication on the current site and have it configured to auto-login. This install has been used as our organization's intranet for the past 2 years.  Two distinct uses of our intranet have emerged since it was installed: internal communications and a portal for applications.  We have done enough customization to this site to convince me that i want to start over with a fresh DNN install on a new server and not attempt to convert/upgrade the site.

Now that we have recognized these two distinct uses, I am moving forward with a new intranet server and have explored multiple options to seperate these DNN uses (multiple parent and/or child portals vs. multiple dnn instances).  I am leaning towards two instances of DNN; this idea was reinforced by reading the following blog:
http://www.willstrohl.com/Blog/EntryI...

I have the new server setup with the environment listed above and have installed two instances of DNN.  Both sites are applications in IIS under the Default Web Site, but are using different app pools (configured the same).   I have enabled AD authentication on both instances and configured to auto-login.  This setup works great on both sites independently; however, i'm having problems when using both sites at the same time.   The 1st site's auto-login work great.  The 2nd site generated the following error:

Unable to validate data.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Unable to validate data.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Unable to validate data.] System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, IVType ivType, Boolean useValidationSymAlgo, Boolean signData) +4295147 System.Web.Security.FormsAuthentication.Decrypt(String encryptedTicket) +351 DotNetNuke.HttpModules.Membership.MembershipModule.OnAuthenticateRequest(Object s, EventArgs e) +710 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171 


Version Information: Microsoft .NET Framework Version:2.0.50727.4952; ASP.NET Version:2.0.50727.4955


If i log out of the the 1st site and refresh the 2nd, the auto login works.  Basically, i can't be auto-logged into both sites at the same time.
I need users to be able to access both sites simutaneously since many users will be looking for internal communications at the same time they are using working on the appliation portal to do their job.  And of course nobody wants to be bothered to login!

So, my main question is "Is this possible?".  Any other opinions on the route and reasoning i'm taking would be greatly appreciated.  I'm guessing my problem has something to do with both sites using the same cookie, but haven't spent much effort exploring this yet.

Thanks to everyone's help on these forums for getting me this far before i had to ask these ?'s.



 
New Post
2/28/2011 10:38 AM
 
Does anyone have experience running multiple instances of DNN on the same server and using AD authentication on both?  I'm surprised this is not more common...or am i missing an alternative way in accomplishing this?
 
New Post
2/28/2011 11:19 AM
 
I suspect it's the cookie as well as I've used sub-portals with the AD provider before without a problem. I've heard of this before with DNN in general and I think the fix at the time was to change the Forms name in the Authentication section from .DotNetNuke to something else (e.g. .DotNetNuke1) in your web.config.
 
New Post
3/2/2011 1:04 PM
 
Thanks for your reply Mike. I had read about the forms name in the web.config file as well. I tried that a couple weeks ago and re-tried today after reading your reply. I changed the name, restarted IIS, & deleted cookies....same error when bouncing back and forth from site to site.
 
New Post
3/2/2011 1:11 PM
 
Thanks for your reply Mike. I had read about the forms name in the web.config file as well. I tried that a couple weeks ago and re-tried today after reading your reply. I changed the name, restarted IIS, & deleted cookies....same error when bouncing back and forth from site to site.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory authentication on multiple DNN instancesActive Directory authentication on multiple DNN instances


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