Utilizando SSL no SiteFinity

1. Modify the web.config wsFederation node :

<wsFederation passiveRedirectEnabled="true" issuer="https://localhost/Sitefinity/Authenticate/SWT" realm="http://localhost"requireHttps="true"/>

2. Add the https:// binding in the list of security token issuers in your SecurityConfig.config:

<securityTokenIssuers>

        <add key="EF2C5C002D2154992CF797F0E074F89262A92AFF6777929FA0CBAF01BF453558" encoding="Hexadecimal" membershipProvider="Default" realm="http://localhost" />

        <add key="EF2C5C002D2154992CF797F0E074F89262A92AFF6777929FA0CBAF01BF453558" encoding="Hexadecimal" membershipProvider="Default" realm="https://localhost/Sitefinity/Authenticate/SWT" />

    </securityTokenIssuers>

    <relyingParties>

        <add key="EF2C5C002D2154992CF797F0E074F89262A92AFF6777929FA0CBAF01BF453558" encoding="Hexadecimal" realm="http://localhost" />

    </relyingParties>

Please keep in mind that the key value will be different in your SecurityConfig.config - use your value, not the one in the example above!

3. Make all backend pages to require SSL - each Sitefinity page has a Require SSL property that can be set from its Title and properties action menu. However if you want to automate the process, you can also set this property through code, for example:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using Telerik.Sitefinity.Modules.Pages;

   

namespace SitefinityWebApp

{

    public partial class WebForm1 : System.Web.UI.Page

    {

        protected void Page_Load(object sender, EventArgs e)

        {

   

            PageManager pageManager = PageManager.GetManager();

            var pages = pageManager.GetPageNodes().ToList();

   

   

            foreach (var page in pages)

            {

                if ( page.Page != null)

                {

                    page.Page.RequireSsl = true;

                }

         

            }

            pageManager.SaveChanges();

        }

    }

}

4. Under Adminsitration->Settings->Advanced->System->Servicepaths ->WorkflowBaseUrl please enter the correct http:// binding for the site (i.e. on my site it's just http://localhost as I have the site running on port :80) - this is necessary so the WorkflowService can be correctly invoked on its correct http:// endpoint, even when under https://

Following these steps should allow you to have the entire backend configured under SSL.