[MAGNOLIA-8704] Changes to IPConfig leads to null pointer Created: 17/Jan/23  Updated: 17/Jan/23

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: 6.2.6
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image.png    
Issue Links:
Problem/Incident
is caused by MAGNOLIA-7957 Support IP ranges in IPSecurityManager Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Reproduce
Try to follow the steps to add another rule.

Expected
I should be able to add a node to /server/IPConfig without bricking the instance.

Actual
Null pointer which leads to inaccessible instance.

Workaround
To avoid the null pointer you can first duplicate the existing "allow-all" node.

Notes
Problem line:

if (ruleIp.contains("/")) 

Blows up if ruleip in null.


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