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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Multiple SSLs on a single DNN install?Multiple SSLs on a single DNN install?
Previous
 
Next
New Post
7/27/2007 7:45 AM
 

Some background: we have a Windows 2003 server with a single IP address and one DNN 4.3.4 installation at present, which has several portals, one of which is an ecommerce site using CataLook module and Protx as the PSP. Due to the limitation of the how CataLook integrates with Protx it is not possible to have more than one Protx account per DNN install unless a third party processing module such as .netCharge is used.

We now need to add a second ecommerce portal and as the client will also be using Protx for payment processing we now have to install .netCharge or set up a second DNN master portal, which I'd rather not do. To use the .netCharge module we need an SSL certificate. We could presumably just set up the SSL for this site's domain but this will cause problems when we come to add another ecommerce site at a later point. I've looked into shared/wildcard SSL certificates but these won't be suitable because each site is on a completely different domain.

Bear in mind that until now I knew sod all about SSL, I'm running to catch up! :o

So, is it at all possible to have multiple SSL certificates for a single DNN installation with multiple sites/portals running from it. If so, how on earth do I go about setting things up!

So far I've tried this:

  • Install and set up DNN on domain1 as a website, not virtual directory
  • Create a second portal in DNN with the host header for domain2
  • Set up a new website in IIS with domain2 as the host header pointing at the exsiting DNN directory
  • Use Microsoft's SelfSSL tool to create a certificate for domain2
  • Attempt to connect to domain2 over https in a Firefox - which worked
  • Then created a second certicate for domain1 and attempted https connection - which worked
  • Then attempted https connections to both sites in Internet Explorer - failed
  • Firefox now cannot connect over https!
  • Removed certificate for domain1
  • Still can't connect over https
  • Removed certificate for domain2 and recreated it
  • Can now connect to domain2 over https
  • Got headache and gave up!

Can someone please let me know if what I'm attempting will work how it needs to work, ie two or more separate domains each with their own SSL running from the same DNN installation.

 
New Post
7/27/2007 8:07 AM
 

SSL certificates on two different domains requires two IIS websites using their own IP address. You can not use Host Headers in IIS to share the IP if you need more than one SSL certificate.  The only way to get around that requirement is to run SSL for another site on something other than the default port of 443 and this is not a good alternative because then it requires the port to be inluded on the Url.

If you are going to be running e-commerce for two different clients then you should set them up on their own IP address with two different IIS websites pointing at two different DNN Install folders and using their own Databases.

Sharing any of the above when doing e-commerce is just asking for trouble.  Especially if your client does not know they are sharing.

 


DotNetNuke Modules from Snapsis.com
 
New Post
7/27/2007 9:05 AM
 

I'd pretty much guessed that would be the case :(

The reason I was reluctant to have a second DNN instance was because of the server resources required. If we have to do this for evey ecommerce site we create then it's going to eating up resources and seriously affecting performance.

 
New Post
7/27/2007 9:29 AM
 

Most hosters that I know of usually have a couple of tiers for their hosting plans to account for the different server requirements for different sites.  A site running any sort of ecommerce has certain security requirements.  These requirements necessarily require more isolation and thus more server resources and the price structure should accomodate this extra expense.  Like John, I don't recommend cutting corners when it comes to e-Commerce security.  Too often consultants try to drive down the costs for our customers but we need to be clear when that lower cost is coming at the expense of an increased security risk.  Ultimately the customer will decide if the increased security is worth the added cost, but it is our job as consultants to give the customer a complete picture so they can make an informed decision.


Joe Brinkman
DNN Corp.
 
New Post
7/27/2007 9:30 AM
 

Can't you set up https://ecommerce1.site.com and https://ecommerce2.site.com ? That won't need separate IP and ports, will they? Is there a problem with set up like that?


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Multiple SSLs on a single DNN install?Multiple SSLs on a single DNN install?


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