How to set this up varies depending on your requirements. It also depends on if you are using multiple portals in your installation.

I generally use www.domain.com for my certificate and also force all requests to this (in a single portal setup, where there is 1 certificate per portal and I am not using a shared certificate or I have no other portals). How I accomplish this is use IIS to redirect all domain.com requests to www.domain.com, then I have my www.domain.com certificate. Then I install the cert to the appropriate site and in DNN I only have my www.domain.com alias here. Next I set my settings (as host) under the Site Settings menu (SSL Settings section). Here I check the SSL Enabled and SSL Enforced checkboxes (which permit SSL, the other forces it so only SSL is used where I want https). I then set the SSL URL to www.domain.com, and also set the Standard URL to this as well. When you are using a shared certificate, or different domains here (ie. secure.domain.com vs www.domain.com) I would use secure as SSL URL and www as Standard (and my certificate would be secure). The problem w/ doing it this way is that users who login on one domain are not logged into the other. Of course, you also have to go to each page you want secured here and check the Secure checkbox. 

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.