Project

General

Profile

Feature #863

Add IP filtering parameter on a per endpoint basis

Added by Mike Stults almost 7 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Mike Stults
Target version:
2.4
Start date:
01/30/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

Web service shell currently uses Tomcat filter, org.apache.catalina.filters.RemoteAddrFilter, as defined in the web.xml file to enable filtering of IPs. As this is tomcat specific code, this feature is not available in Glassfish. In order to provide an IP filtering feature for both Tomcat and Glassfish, add a new capability to filter IPs, and additionally, make it available per endpoint.

History

#1 Updated by Mike Stults over 6 years ago

  • Resolution set to Fixed

2017-04-06 7e962ce (Mike Stults): -- issue 863 - did a rename from allowIPs to allowedIPs in this commit, filters both per endpoint and for builtin, global endpoints like wssstatus
2017-02-03 5fea5a1 (Mike Stults): -- issue 863, IP filtering - is functionally complete unless a problem shows up, many println need to be removed, possibly change allowIPs to allowedIPs, how to report rejected IPs
2017-01-30 4c03772 (Mike Stults): -- issue 863, prototype CIDR code using edazdarevic code for IPv4 and IPv6 IP filtering

Example for using this feature to restrict access to wssstatus, add this line to service.cfg
wssstatus.allowedIPs=127.0.0.1/32,::1/128

#2 Updated by Mike Stults about 6 years ago

  • Target version set to 2.4

Also available in: Atom PDF