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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trying To Force DNN 6.2.x to FORCE SSL page to "SECURE"Trying To Force DNN 6.2.x to FORCE SSL page to "SECURE"
Previous
 
Next
New Post
8/4/2014 6:24 PM
 

Need some help on this one.

Recently in 6.2.x  even after you enforce SSL on the entire site, you often have to go to individual pages and click the check box AGAIN on each separate page as "SECURE". Which is very time consuming for larger sites... sure SSL in forced but some individual pages are still not SSL.

What would be a sure fix to force SSL on all pages without "Admin" having to go to every single page and clicking on the SSL check box under "page settings" again?

If possible, is there a DB script that can be run that would prevent me from having to physically go and change every single page to click the "Secure" checkbox?

Please Advise as soon as possible... 
Thanks..

 
New Post
8/4/2014 6:45 PM
 
Hello,

I might be wrong about this, but I think that "Enforce SSL" doesn't do what you're thinking... I think that it just means that DNN will force the user into the state set on the page. So, if you have "Enforce SSL" set, then a user who browses to a non-secure page over https will get it over http.

If that's right, then you'd need to just mark all the tabs as "Secure" - you're right that can be easily done with an SQL script. It would be a very simple script, actually... something like "update Tabs set IsSecure = 1"

But, you might hold off on executing that and see if somebody else has a different thought on this.

Mike
 
New Post
8/4/2014 7:34 PM
 

What happens is when a page request is made DNN evaluates what protocol it currently is (i.e. http or https), and whether the page is marked as secured or not. It then uses the values for ssl enabled and ssl enforced to determine the final page url using these rules:

• if ssl enabled for a site and a page that is loading is marked as secure but is currently loading as http, it will redirect to the https equivalent

• if ssl enforced for a site, and a page that is loading is not secure but is currently loading as https, it will redirect to the http equivalent

In other words if a site is ssl enforced it will only load pages marked as secure via HTTPS, all other pages will load as HTTP


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/5/2014 1:39 AM
 
Okay understood and thanks for the explanation... but what would be the quickest way to mark all my pages as secure with a SQL script like Mike was saying?

I am aware I would have to back my site up first before running such a script but i like Mikes idea. I just need help with the exact SQL script syntax that would do the trick and mark all my pages as SECURE without having to go to each page. 

Please advise with a safe script I can use.

 

 
New Post
8/5/2014 2:52 AM
 
you may run the following statement in Host > SQL to enable SSL for all pages of a website (replace trailing 0 with ID of your website):
UPDATE {databaseOwner}[{objectQualifier}Tabs] SET IsSecure = True WHERE PortalID = 0

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Trying To Force DNN 6.2.x to FORCE SSL page to "SECURE"Trying To Force DNN 6.2.x to FORCE SSL page to "SECURE"


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out