Anjali,

I would suggest to implement HSTS (HTTP Strict Transport Security) - that should solve the problem, as all insecure requests to the server will be upgraded. It is just adding a response header - see https://scotthelme.co.uk/...tp-response-headers/ for more information.

Happy DNNing!
Michael

PS: Please ignore the section about Public Key Pinning in the linked article - this is a bad idea, as it contains some risks. The article is from 2015, and PKP is not recommended anymore.

Michael Tobisch, Getting same issue when I applied that "custom http Response header" setting in IIS that you suggest

for "HTTP Strict Transport Security" into https://scotthelme.co.uk/...tp-response-headers/

 

 

Anjali,

maybe this is too less. Have you tried implementing a rewrite rule that changes http to https?

[rewrite]
   [rules]
      [rule name="HTTP to HTTPS redirect" stopProcessing="true"]
         [match url="(.*)" /]
         [conditions]
            [add input="{HTTPS}" pattern="off" ignoreCase="true" /]
         [/conditions]
         [action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" /]
      [/rule]
   [/rules]
[/rewrite]

Please note: For IIS previous to version 10.0 1709 it is necessary to install the Url Rewriter Module for IIS to make this work. And I used square brackets instead of angle brackets here, as the code will not display otherwise...

Happy DNNing!
Michael

If you ssl termination is not in iis (load balancer or reverse proxy or some such) you need to set an https header and configure that in Dnn ssl settings. Not sure if that is your problem, but might work checking...