-
Bug
-
Resolution: Done
-
Minor
-
3.0.0.Alpha11
-
None
Management model does not validate input values for attributes in /interface section.
Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or it the address fits in the given subnet definition. Value is a network IP address and the number of bits in the address' network prefix, written in "slash notation"; e.g. "192.168.0.0/16". An 'undefined' value means this attribute is not relevant to the IP address selection.
In the description of subnet-match attribute it is clearly defined the format of input value. However the following command does not fail.
/interface=public:write-attribute(name=subnet-match,value="wrong-input") { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
Attribute indicating that part of the selection criteria for choosing an IP address for this interface should be whether or not the address matches the given value. Value is either an IP address in IPv6 or IPv4 dotted decimal notation, or a hostname that can be resolved to an IP address. An 'undefined' value means this attribute is not relevant to the IP address selection.
There are also attributes which accept inet addresses - namely inet-address, loopback-address. Validation for these attributes is not performed either.
/interface=public:write-attribute(name=inet-address,value="wrong-input") { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
- is cloned by
-
JBEAP-6812 Management model does not validate input values in interface section
- Closed