The Mighty Blog

Jan11

Written by:Will
1/11/2008  RssIcon

As of version 4.06.02, DotNetNuke (DNN) has the built-in capability of providing a Secure Socket Layer (SSL) connection for any page on the web site. Some of you may notice such a page when the little lock appears on your web browser, and the prefix for the URL is "HTTPS" instead of "HTTP". Doing this for your DNN web site is pretty simple.

As of version 4.06.02, DotNetNuke® (DNN) has the built-in capability of providing a Secure Socket Layer (SSL) connection for any page on the web site.  Some of you may notice such a page when the little lock appears on your web browser, and the prefix for the URL is "HTTPS" instead of "HTTP".  Doing this for your DNN web site is pretty simple.

Please NoteYou should only enable SSL for pages that display or ask for sensitive information.  All other pages will be much faster without it.

First of all, you need to have an SSL certificate installed on your server, and it needs to be available for your domain.  Acquiring one and installing it is beyond the scope of this post, but a quick search on Google should get you going for either task.

Once you have SSL installed on your web server, you need to proceed with enabling it on DNN.  If you don't, the UrlRewriter will keep reverting all HTTPS requests to HTTP.  In order to do this, you must login as a "Host", and go into the "Site Settings" page in the "Admin" menu.

If you scroll down, you will find a section inside the "Advanced Settings" area called "SSL Settings".  It will only be available to you if you are logged in with a host account.

SSL Settings - Found in Admin menu > Site Settings page > Advanced Settings

In the "SSL Settings" section, check the checkbox labeled "SSL Enabled?".

I also would suggest checking the checkbox below it.  It is labeled "SSL Enforced?".  The logic of the labeling is a bit backwards.  If you check that checkbox, the only pages that will be allowed to use the SSL protocol are ones where the "Page Settings" says to.  This is what you want.  Otherwise, after you go to the first SSL page, all subsequent page requests will continue to use the SSL protocol. 

The next two fields only apply to those using a hosting provider.  Contact your hosting provider for this information.

Now, create a new page on your portal.  The location doesn't matter, but be sure that you uncheck the checkbox for "Display In Menu".  Name this page something like "Site Login".  Also, check the "Secure?" checkbox in the "Advanced Settings". 

Other Settings - Found in Page Settings > Advanced Settings

Once you are viewing the page, add the "Account Login Module" to it.  Now, logoff and click the "Login" link on the web site.  You should be looking at a secured page!

2 comment(s) so far...


Gravatar

I'm looking at a redirect loop error.
I remember that in DNN 4xx I had a query string flag I could use to turn off the SSL...
Buggered if I can remember it though...
Nobody online seems to remember it either..

By Dooley on   4/10/2009
Gravatar

Great question! You can do that using ssl=1 in your URL. For example:

www.dotnetnuke.com/Default.aspx?ctl=login&ssl=1

By Will on   4/10/2009

Your name:
Gravatar Preview
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Comment:
Security Code
CAPTCHA image
Enter the code shown above in the box below
Add Comment   Cancel 
Add to Technorati Favorites
Tweet about my blog
Will Strohl - The Mighty Blog - RSS Feed

Tag Cloud

Sort by:Tag | SizeRSS
camp   community   dnn   dotnetnuke   dotnetnuke®   event   example   free   get   group   integer   jquery   meeting   module   odug   orlando   search   session   think   use  
The opinions expressed here are the personal opinions of Will Strohl and do not necessarily represent the views and opinions of the DotNetNuke Corporation.
© Copyright 2004-2010 by Will Strohl. All rights reserved.Website Skinned By: Ralph Williams  Website Hosted By: Applied Innovations