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...Tutorial on setting up SSL in DNN 4.5.4+Tutorial on setting up SSL in DNN 4.5.4+
Previous
 
Next
New Post
8/4/2007 1:35 PM
 

If you are going to secure many subdomains / hostnames on a single domain then you probably need what is known as a wildcard certificate.  This may be overkill though.  You could just get one certificate for "secure.customerdomain.com" and make sure that all secure traffic is handled through that.  Keep in mind though, if you are going to secure the input on login, then you will need to secure the actuall hostname.domainname they will be logging into, otherwise the user will not be logged in when they move back to a different hostname.  In that case, you are back to using a wildcard cert if you want to secure several hostnames / subdomains.

 

 


DotNetNuke Modules from Snapsis.com
 
New Post
8/4/2007 7:36 PM
 

Thanks John, one other quick question. Assuming my customer's portal is www.customerdomain.com for straight HTTP and the secured pages are under another alias, such as HTTPS customerdomain.mydomainname.com(where wildcardssl is applied), how do you make the menu item that would be a secured page, switch alias names when the user clicks it? The only thing I can think of is make the menu item tab a redirect to the HTTPS page tab which I would make hidden or something.

Thanks

 

 
New Post
8/4/2007 9:32 PM
 

Yes, creating a menu item that points directly to the SSL channel would be a good way to switch on. You may also need a way to switch SSL back off if they go to non-secure pages though, and the Enforce SSL setting in admin > Site Settings should take care of that.

If you have several pages that should be secured using the same alias (host.domain) then you may want to make use of the SSL Url under Admin > Site Settings. I haven't don't extensive testing of this setting, but that is my understanding of how it is supposed to work.


DotNetNuke Modules from Snapsis.com
 
New Post
8/4/2007 9:38 PM
 

I just realized that you may have been asking how to actually create the menu item that goes directly to an HTTPS page. You can do that in the Page Settings by making it point using the Link Url setting and making it Url (A link to an external website).  Even if it is pointing to a tab on your same portal this is a good way to specify exactly what you want the Url to be.


DotNetNuke Modules from Snapsis.com
 
New Post
5/2/2011 12:13 PM
 
The link posted on the first page by John Mitchell does not work. I get the error message saying... you do not permission to access this tab

One more question, something I have been struggling with:

the bottom line is that DNN 5 has SSL support and we DOT NOT have to buy modules like SSLRedirect or SSL_Module. Is that a right assumption?
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Tutorial on setting up SSL in DNN 4.5.4+Tutorial on setting up SSL in DNN 4.5.4+


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