-
Bug
-
Resolution: Unresolved
-
None
-
unspecified
-
None
-
Operating System: All
Platform: All
-
7902
Hi,
Steps to recreate -
1) when i am trying to set the following value of ACP:
"pv":{"acr":[{"acor" : ["admin"],"acop":63,"acco":[{"acip":{"ipv4" : ["10.125.0.0/16","127.0.0.1"]}}]}]},"pvs":{"acr":[{"acor" : ["admin"],"acop":63,"acco":[{"acip":{"ipv4" : ["10.0.0.2","127.0.0.1"]}}]}]}
2) I am seeing following error message.
Cannot update this resource [400] :
Actual behavior -
IoTDM is not allowing to set the CIDR suffixed ipv4 address (or subnet ip) for the element "accessControlContext/accessControlIpAddresses/ipv4Addresses"
under ACP resource.
Expected behavior -
As per spec TS-0004: "accessControlContext/accessControlIpAddresses/ipv4Addresses" is the list of type - m2m:ipv4
Table (Table 6.3.3-1) m2m:ipv4
IPv4 address string with optional CIDR suffix 10.125.0.0/16,122.77.12.1
We need to correct this behavior and allow supporting of subnet (CIDR based suffixed) based IPv4 address while creating ACP resource with IPv4 address.