[MAGNOLIA-7957] Support IP ranges in IPSecurityManager Created: 09/Dec/20  Updated: 17/Jan/23  Resolved: 19/Jan/21

Status: Closed
Project: Magnolia
Component/s: security
Affects Version/s: 6.2.5
Fix Version/s: 6.2.6

Type: New Feature Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Done Votes: 0
Labels: ipconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MAGNOLIA-8704 Changes to IPConfig leads to null poi... Open
Relates
relates to MAGNOLIA-1617 Extract ip security out of URISecurit... Closed
relates to MAGNOLIA-7958 Sound defaults for IPConfig rules Accepted
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Date of First Response:

 Description   

IPSecurityManagerImpl has been backed by a mere HashMap (fixed IP or * -> rule) forever.

Although not a widely used feature (and trend goes further towards filtering IPs on a higher level, in front of Magnolia itself), it is quite error prone in its current incarnation.

In particular, support for IP ranges appears missing. Without explicit support, developers are led to believe they can use the wildcard * character which is not supported.


Generated at Mon Feb 12 04:28:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.