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...Same shared SSL for different parent portalsSame shared SSL for different parent portals
Previous
 
Next
New Post
12/17/2008 3:39 AM
 

I would like to use a single shared ssl for different parent portals, each one having its own domain name. Can DNN support the following:?

1- Install a cert, secure.domain1.com in IIS for the default dnn site.

2- Create a portal alias secure.domain1.com in the default portal.

3- Create parent portal called domain2.com and create another alias in this portal called secure.domain1.com/domain2.com

4- Create parent portal called domain3.com and create another alias in this portal called secure.domain1.com/domain3.com

If I want to use SSL for domain2.com for some pages, can the Secure SSL for that site be 'secure.domain1.com/domain2.com' and it works?

 

 
New Post
12/17/2008 10:41 AM
 

Salama wrote
 

If I want to use SSL for domain2.com for some pages, can the Secure SSL for that site be 'secure.domain1.com/domain2.com' and it works?

Not if you use a parent portal, your cert is normally for a specific domain.  You would be using the main portal for part of the domain2 portal's pages.  Possible, but it won't use anything from the domain2 portal, user accounts, permissions, etc. won't carry across.

Jeff

 
New Post
12/17/2008 12:04 PM
 

So what you're saying is that DNN can't match an alias like secure.domain1.com/domain3.com and know which portal it's for? Is the matching done for the whole url or only the domain name part of it?

I know a cert is for a specific domain name but on non DNN IIS sites, the same cert can be used for different sites which are in different domain names as long as you can create a virtual directory in the secure site which points to a folder where the other site resides in. So something like 'secure.domain.com/another domain' points to the folder of 'anotherdomain'. This is done in IIS Manager.

I want to know if a similar thing can be done in DNN using host aliases.

This post indicates someone did it. Now I am getting conflicting stories.

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/248757/scope/posts/threadpage/2/Default.aspx

 

 
New Post
12/17/2008 1:02 PM
 

I've recently just did it.

The following sites:

https://www.DNNReactor.com

https://www.Rad-Websites.com

and

https://www.MusicianHouse.com

are all runnign on the same instance of DotNetNuke on one server, using one SSL certificate for all three.   SSL really has nothing to do with DotNetNuke so much....each page can be SSL or not, with a click of a mouse in DotNetNuke.  The snag is in IIS.

Now in a scenario like this, there is only one downfall that I can see off hand.  I use GoDaddy for my SSL certificate, and even though it's valid on all three sites(actually up to 4 or 5 I can use this cert on), the "site seal" that godaddy gives you, only shows the first domain name, so on www.rad-websites.com if I had a site seal installed, it'd still say www.dnnreactor.com

Take a look at this page: http://www.musicianhouse.com/Buy/tabid/1169/List/0/Default.aspx

On the left pane, bottom position, you'll see the godaddy site seal, and it tests valid and safe, but everything points to another domain name(dnnreactor).

So, if planning to use a "site seal" on the sites, I'm not sure what sort of "sense" that gives the end user who's lookign for a sense of security...But, the site loads up in IE, or any browser I use, secrue, with no warnings or errors....so if your not using a "site seal" on your site to give people a cozy feeling, then there is no issue doing it this way at all..

 

Back to it, you generate your new SSL cert request in IIS, save the text, go over to godaddy, and buy the....."Multi Domain UCC" version of the SSL certificate.  They have very detailed instructions on how to install it on your IIS and it' goes very smooth.  They have different "extras", I just got the "standard SLL" package, with multi domain support.  you have to look at your case and determine where you fit best.

install it, and whatever sites you have associated to that Multi cetificate, will work, no problem, secured in DotNetNuke, when you set the checkbox under the host menu to allow SSL.

Now, on the negative end, any sites that decide, on that instance to use SSL, but are not assigned to the certificate on godaddies end, willl go secure, but give so many red lights and warnings to the end user that they can't even figure out where your site went :->

 

Anyhow, once you do it one time, it's really simple, but the first time can be confusing and seem more intimidating that it is.  If you want, go to one of my websites, I guess DNNReactor is the best place, register wiht a valid email address and post me in the forms that you want me to help you and I will...no charge.  I'd say just email me at "blahblah" but I don't like robots that grab my email address and start spammign me :-> 

 

Anyhow it's easy, let me know if I can help, I'll walk you through it over IM, email, phone, whatever.

 

 

 


Josh Martin

 
New Post
12/17/2008 4:30 PM
 

A UCC cert sounds interesting but I don't it will fit my need. I am planning to host many sites and the cert will get pretty expensive once I go beyond 5 sites. Plus it's not clear on GoDaddy's site if the all domain names need to be known before you get the cert. I am setting up SSL sites as users ask for them so it's not a one shot batch thing.

I really want to use a single cert and know if it can work for many parent portals.

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Same shared SSL for different parent portalsSame shared SSL for different parent portals


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