Version Sitefinity 14.0
Sitefinity 14.4 Sitefinity 14.3 Sitefinity 14.2 Sitefinity 14.1 Sitefinity 14.0 Sitefinity 13.3

Topics

All topics

Security and load balancing

Shared encryption

To ensure that Sitefinity CMS uses the same encryption key when running in load balancing, it is required that all web servers use the same machine key.

You must add a machineKey configuration in each instance’s web.config file.

NOTE: Add the machine key inside section <configuration>/<system.web>. This is the <system.web> section that is a direct child of the <configuration> section.

For more information, see Microsoft's machineKey Element (ASP.NET Settings Schema) .

SSL and load balanced scenario

If you have an SSL binding for your site, you must have the SSL certificate installed on each of the web server nodes and must have added the https:// bindings to the configurations listed in the procedure above.

If you want to have Sitefinity’s Login page to be served under https://, perform the following:
  1. Open the web.config file of each instance participating in the load balancing configuration. 
  2. Navigate to the <wsFederation> node in the file and set the requireHttps parameter to true.
    For example, <wsFederation passiveRedirectEnabled="true" 
    issuer="http://localhost" realm="http://localhost" requireHttps="true"/>

NOTE: Sitefinity CMS does not synchronize its configuration between the nodes participating in your Load Balanced setup. You must perform the above settings on all Sitefinity CMS instances of your load balanced setup. If you are interested in possible approaches for handling configuration synchronization, see Administration: Upload and physical location of the application.

Want to learn more?

Sign up for our free beginner training. Boost your credentials through advanced courses and certification.
Register for Sitefinity training and certification.

Was this article helpful?

Next article

Setup Site Sync with load balancing