tracker issue : CF-4106021

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: CF Admin still mentions iprestriction.properties

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 01/11/2016

Components: Administrator

Versions: 11.0

Failure Type: Cosmetic Issue

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Minor / Very few users will encounter

Locale/System: English / Platforms All

Vote Count: 0

Listed in the version 2016.0.03.300466 Issues Fixed doc
CF Admin still mentions iprestriction.properties

Repro: See "Allowed IP Addresses" page of CF Admin says:

-----------
If you have configured an external web server, you can also restrict access to the ColdFusion Administrator and ColdFusion Internal Directories at the connector-level by modifying the iprestriction.properties file available under the connector folder. For instance, cf_root/config/wsconfig//iprestriction.properties.

Note : You will need to restart the external web server after modifying the iprestriction.properties file. 
-----------

That wording should be removed b/c that file is no longer installed, and no longer works, as of CF11 Update 3.

To verify, w/ IIS:
1) Add the following line to C:\ColdFusion11\config\wsconfig\1\isapi_redirect.properties: ip_restriction_file= C:\ColdFusion11\config\wsconfig\1\iprestriction.properties
2) Create C:\ColdFusion11\config\wsconfig\1\iprestriction.properties having this line: */CFIDE/*=127.0.0.1,::1
3) Restart IIS (I also restarted CF for good measure)
4) See CF Admin is still accessible from other IPs (meaning, this file doesn't even work - so that wording should be removed from CF Admin's "Allowed IP Addresses" page)

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4106021

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email:

Attachments:

Comments:

This issue is fixed now. The fix for this issue will be available as part of ColdFusion 2016 Update 3.
Comment by Nimit S.
4898 | June 14, 2016 01:52:34 AM GMT