Require SSL for a content page requires the Sitefinity editing backend to run SSL as well
When selecting a Sitefinity page for editing that has the "Require SSL" attribute set to true, this forces the Sitefinity backend to attempt to open the Sitefinity editing screens over SSL as well. This poses a problem when moving between development and production environments. The development environment does not have an SSL certificate (using the built in Sitefinity Project Manager web server), while the production environment does have an SSL certificate.
Is there a way to resolve this without having to install an SSL Certificate in development just to edit my Sitefinity content pages?
Hi Samir,
You need to enable SSL in IIS, but you don't need to purchase a separate certificate to do so. It's explained here and it works fine.