Dotnetnuke has a pretty good system for utilizing SSL with your Dotnetnuke site.  The implementation is straight forward and easy to use.  I will attempt to give a high level summary of how easy it is to use SSL with your Dotnetnuke site.  This tutorial will assume you already have setup and configured your SSL certificate correctly on your server or with your hosting company.

1. Login as a user with "Host" level privalages.
2. Navigiage to Admin | Site Settings
3. Expand the "Advance Settings" section
4. Expand the "SSL Settings" section
5. Put a check next to "SSL Enabled"
6. OPTIONAL: You can put a check next to "SSL Enforced".  This basically if a page isn't set to be secure then it won't ever be secure.
7. Enter your SSL URL in the text box provided (Example for a shared certificate you might put: si-eioswww4.com/hilbertsolutions-com)
8. Enter your Standard URL in the text box provided. (Example would be www.hilbertsolutions.com)
9. Click the Update button.

Now that you have configured the site for SSL you need to tell which pages on the site should utilize SSL.  To do this you do the following:

1. Navigate to the page you want to utilize SSL.
2. In the control panel click on "Settings".
3. Expand the "Advanced Settings" section.
4. Under the "Other Settings" section put a check next to "Secure"
5. Click Update.
6. The page will now switch to SSL when navigated to.

Having to do this on a page by page basis provides a great level of customization, however, it can be repetitive as well.  Here is a little SQL statement I run to help speed the process up consideribly.

UPDATE [Tabs]
   SET [IsSecure] = 'true'
 WHERE TabID = 100

TabID is the number that represents a page.  You can usually find it in the URL when you are on a page right after tabid.

You can run this script by navigating to Host | SQL and copying and pasting the text into the box and executing it.

You should backup your database before ever running any SQL code against the database. 

Hilbert Solutions, LLC is not responsbile for any damage that might occur from the content of this blog post.