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...Core SSL and why our team has not chosen it, yet.Core SSL and why our team has not chosen it, yet.
Previous
 
Next
New Post
9/10/2007 5:02 PM
 

Well having browsed for a Core SSL forum and not finding it, I will post this here.

My team felt we should express our decision not to switch to Core SSL from the 3rd party module we currently use for secure redirection, in the interest of giving the Core Team some feedback that could improve the upcoming versions of the feature.

Core SSL Pros:

1. Extremely easy to install and use. Having the option to one-click secure any page from its page settings is just great. Granted, our 3rd party module also allows us to do this, but at least you guys didn't change the bits just to say you had different bits.

2. Installation, testing, and implementation never gave a hint of causing lockouts/oddities/site failures of any kind. Was 100% reliable even with a noob at the controls.

I must say ,some oddities in the 3rd party module we are using have caused me to restore a previous web.cfg THREE TIMES, in order to return the site to proper working order. This is despite me reading step by step in their manual.

Core SSL Cons:

1. Honestly we only have the one, at the moment. It would be really nice to have a 'parameters' section available somewhere. So that we can properly secure dynamically created pages, such as the user editing their profile, in the forums area. Using the parameters section of our 3rd party module, I was able to do this in short order. Using Core SSL, when I did this the only way allowed(going to page settings while in my Edit Profile page on the forums), it simply redirected ALL links on the forum, to https.

What we would like to see:

In addition to fixing the one 'con', we would love to see also some options for rewiting links to the css and images, to remove the 'Mixed Content' messages. This is not a pressing issue; to avoid any possible problems, we don't use it on our site, tho our 3rd party module does allow us to.

In closing, great work on the SSL Module, I am sure many use it and love it, and if you can keep things as simple and reliable as they are in this version, while adding some future, we would LOVE to switch to Core SSL in the future.

-J.C.

 
New Post
9/10/2007 6:45 PM
 

Hi Jeff, I'm not quite sure what you mean, the core SSL solution does support page level SSL (if you look @ http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1501/Default.aspx you'll see screenshots and details of this). If i'm not understanding your request, please log an enhancement request @ http://support.dotnetnuke.com/project/Project.aspx?PROJID=23 and perhaps it'll be added in a future dotnetnuke release.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
9/11/2007 9:04 AM
 

Cathal,

Isn't the "Secure" check box in Page Settings the mechanism for page level SSL?

 
New Post
9/12/2007 9:42 AM
 

Cathal,

Thanks I will check that link see what it says.

Perhaps it would be easier to configure this module if it had a 'projects' section on this website, like other modules, and perhaps somewhere I could get instructions other than someone's blog?

I did find it annoying that to get setup instructions I had to do a google search and read someone's blog. It's an important module and should be documented like the others.

 
New Post
9/12/2007 9:47 AM
 

Cathal,

We aren't talking about basic page level security. We are talking about being able to set parameters, so that anytime several different parameters are in place, the site secures those pages.

This is important because you can say no matter who is logged in, when such and such is in the address, make that page secure. Our current 3rd party module lets you do this, Core does not, yet.

If you still do not understand, then I will repeat my example: when I go to my edit profile page on our forums, and then go to page settings, and secure that page, EVERY page for EVERY user, EVERYWHERE on the forum, is now secure. I do not want that. I want it to secure the page only when a user goes to edit their profile on the forum(to protect data sent).

Our current 3rd party module allowed me to do this by setting a custom list of parameters under which it will automatically secure a page.

Understand?

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Core SSL and why our team has not chosen it, yet.Core SSL and why our team has not chosen it, yet.


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