I have CF installed on an IIS-based server hosting multiple
Web sites; not all of those Web sites even use CF. Let's call the
server "server1.my.com", and the sites are hosted as
"site1.my.com", "site2.my.com", etc.. Let's further assume that I
have a couple dozen fairly low-traffic sites hosted on this same
box in this same manner. (I mention this only as background, and
because I am hoping not to saddle myself or my server admin with a
significant maintenance effort as sites come and go on this box.)
What I'd like is to have the CF administrator interface available only as server1.my.com/CFIDE/Administrator/index.cfm and to have access to the CF admin restricted to a specific set of IP addresses. In addition, I want that to be the /only/ way in which the CF administrator can be accessed.
I have the first part of that set up, and the IP-based restriction seems to work fine. What I can't find a way to do is the elimination of access to the CF administrator on all of the other Web sites hosted on this same box. I can, for example, pull up the CF administrator as site1.my.com/CFIDE/Administrator/index.cfm or site2.my.com/CFIDE/Administrator/index.cfm, etc., regardless of what IP I am requesting it from. I can do that even for sites hosted on the box that don't use CF.
(I am a little hamstrung here because I don't have access to the IIS administrative console, but have to rely on a server admin to make changes there. I will also be the first to admit that I am not an IIS expert by any stretch of the imagination.)
The CFIDE folder is set up as a virtual directory on IIS under the server1.my.com configuration, but is not set up as a virtual directory for any of the other sites hosted on the box. We've checked the IIS configuration for all of them.
Questions:
1. Given the above, why is IIS providing site1.my.com/CFIDE/Administrator/index.cfm when there is nothing there as far as a virtual directory AND given the IP address restriction? (There is clearly another path that stuff is going through here, when site1.my.com/CFIDE/Administrator/index.cfm is requested versus server1.my.com/CFIDE/Administrator/index.cfm.)
2. More importantly, what do we have to do to the IIS and/or CF server configuration to achieve what I have outlined?
Thanks for any insight any of you might offer. I've done some digging for recommendations in the Adobe tech notes and here on the forums and haven't really found something that specifically addresses this situation.
--
/ron
What I'd like is to have the CF administrator interface available only as server1.my.com/CFIDE/Administrator/index.cfm and to have access to the CF admin restricted to a specific set of IP addresses. In addition, I want that to be the /only/ way in which the CF administrator can be accessed.
I have the first part of that set up, and the IP-based restriction seems to work fine. What I can't find a way to do is the elimination of access to the CF administrator on all of the other Web sites hosted on this same box. I can, for example, pull up the CF administrator as site1.my.com/CFIDE/Administrator/index.cfm or site2.my.com/CFIDE/Administrator/index.cfm, etc., regardless of what IP I am requesting it from. I can do that even for sites hosted on the box that don't use CF.
(I am a little hamstrung here because I don't have access to the IIS administrative console, but have to rely on a server admin to make changes there. I will also be the first to admit that I am not an IIS expert by any stretch of the imagination.)
The CFIDE folder is set up as a virtual directory on IIS under the server1.my.com configuration, but is not set up as a virtual directory for any of the other sites hosted on the box. We've checked the IIS configuration for all of them.
Questions:
1. Given the above, why is IIS providing site1.my.com/CFIDE/Administrator/index.cfm when there is nothing there as far as a virtual directory AND given the IP address restriction? (There is clearly another path that stuff is going through here, when site1.my.com/CFIDE/Administrator/index.cfm is requested versus server1.my.com/CFIDE/Administrator/index.cfm.)
2. More importantly, what do we have to do to the IIS and/or CF server configuration to achieve what I have outlined?
Thanks for any insight any of you might offer. I've done some digging for recommendations in the Adobe tech notes and here on the forums and haven't really found something that specifically addresses this situation.
--
/ron