-
New Feature
-
Resolution: Done
-
Neutral
-
6.2.5
-
-
Empty show more show less
-
Yes
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.
Acceptance criteria
- causes
-
MAGNOLIA-8704 Changes to IPConfig leads to null pointer
-
- Open
-
- relates to
-
MAGNOLIA-1617 Extract ip security out of URISecurityFilter
-
- Closed
-
-
MAGNOLIA-7958 Sound defaults for IPConfig rules
-
- Accepted
-
