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.
For more information, see https://msdn.microsoft.com/en-us/library/w8h3skw9(v=vs.100).aspx .
NOTE: The following section applies to SWT authentication scenarios and does not apply for OpenID authentication.
For Sitefinty’s claims-based authentication mode to operate correctly under load balancing, you must configure each node participating in the LB configuration as an issuer and as a relying party. For more information about authentication modes, see Authentication and Single Sign-On (SSO).
To add your nodes as issuers and relying parties perform the following:
NOTE: If your site is accessible via www. You must also perform Step 5 for this binding.
For example, http://www.smith.telerik.com/Sitefinity/Authenticate/SWT
NOTE: If your site is accessible on https://, you must perform Step 5 for the https:// binding. You must also add an entry for https://localhost.
You could also use the server IP address:
NOTE: If your site is accessible on https://, you must perform Step 10 for the https:// binding. You must also add an entry for https://localhost
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.
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.
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important