This topic describes how to secure the user interfaces to prevent unauthorized users to access, for a solution with physical separation of servers (decoupled setup).
If you are running Optimizely Digital Experience Platform (DXP), see Securing edit and admin user interfaces.
The considerations below apply for solutions with physically separated servers:
- Have separate servers for the user interfaces and the public site, and have the UI server on an internal protected network.
- Remove access to editing and administration interfaces.
- Remove access to any custom Edit/Admin plug-ins from the public facing server (for example by removing the files).
- If you cannot have separate servers, you should have separate bindings in IIS for the public site and the UI, and use SSL on the UI-binding.
Removing access to editing and administration interfaces
The following description shows how to make the edit/admin user interfaces unavailable on a publicly facing server.
In web.config, both for <location path="EPiServer"> and <location path="EPiServer/CMS/admin">, remove any allow roles (WebEditors, WebAdmins, Administrators and additonal ones) so that the <authorization> sections only contain the following:
<authorization> <deny users="*" > </authorization>
Securing the editing and administration interfaces
Optimizely CMS allows relocation of the edit and admin folders to custom folder names and configurable HTTP ports, to make it harder for intruders to try to access sensitive resources.
Renaming the UI Folder
- Change the uiUrl attribute of the applicationSettings element in the web.config to a custom name:
If you want to secure the UI folder on another port other than that the site is running on, add an absolute URL including a port other than 80 (or a port the application is running on) as shown.
Setting uiUrl to a custom host and port is not recommended for multi-site setups since each site have custom domains. Consider having a separate editing server instead and remove access to editing and administration interfaces on publicly facing server.
- Change the UI provider virtual path attribute from the previous value, for example from ~/EPiServer to ~/newuipath.
<add virtualPath="~/newuipath/" physicalPath="Modules\_Protected" name="ProtectedModules" type="EPiServer.Web.Hosting.VirtualPathNonUnifiedProvider, EPiServer.Framework" />
- Change the location element path attribute from UI to newuipath:
- Change the location element path attribute from UI/admin to newuipath/admin:
- Change the protected modules root path to newuipath:
<episerver.shell> <publicModules rootPath="~/modules/" autoDiscovery="Modules" /> <protectedModules rootPath="~/newuipath/">
- Add a specially designated (and restricted) port for access in the Internet Information Services (IIS) for the site (used for the UI folder in the step 1 above, port 8888 is used for uiUrl). Access to this port could then be restricted (this step can be omitted if you only want to change the folders).
Add support for SSL
Use SSL (Secure Sockets Layer) to secure the website and/or UI folder; see the information in the following links:
Last updated: Oct 30, 2017