Installation and deployment Questions on installation, system configuration and deployment to the live server.
Version 5.x > Installation and deployment > Restricting CMS to Internal View modes: 
User avatar
Member
Member
ZachW - 12/6/2011 9:43:34 AM
   
Restricting CMS to Internal
We currently have 2 production servers in a farm that are linked to a production Db. We'd like to restrict access to the login page and CMS to internal IPs only. We're trying to stay away from having a Staging server so that our end users don't have to remember to got to a different address/server to make changes. What's the best way to accomplish this?

User avatar
Kentico Consulting
Kentico Consulting
kentico_borisp - 12/7/2011 6:12:57 AM
   
RE:Restricting CMS to Internal
Hello,

The easiest and most straight forward approach would be to add some logic into the Global.asax.cs file (\App_Code\Application\CMSAppBase.cs file for 6.0) where you would check the domain of the incoming request and the URL of the request. If the URL contains the CMSDesk or CMSSiteManager sub-string, you will check for the IP from which the request came. If the if the IP isn't from your internal network, you can display an error message or redirect the user to teh home page.

This check can be done in the Application_BeginRequest() method.

Best regards,
Boris Pocatko