Policies can restrict access for NGSI requests only to certain attributes.
Per default, it should be possible to restrict access directly on attribute level, as it is implemented right now.
In addition, it should be possible to restrict attribute access also to "sub-attributes", e.g. unitCode for attribute temperature.
It needs to be investigated first, how this could be configured (e.g. flag in API Backend UI) and whether this required.
Also it needs to be investigated how to model this in the policies, e.g. by dot-separation: temperature.unitCode in the attributes list array of the policy.
The attribute evaluation function needs to be modified for that has been added to the utility module implemented in #16 .
Policies can restrict access for NGSI requests only to certain attributes. Per default, it should be possible to restrict access directly on attribute level, as it is implemented right now. In addition, it should be possible to restrict attribute access also to "sub-attributes", e.g. unitCode for attribute temperature.
It needs to be investigated first, how this could be configured (e.g. flag in API Backend UI) and whether this required. Also it needs to be investigated how to model this in the policies, e.g. by dot-separation: temperature.unitCode in the attributes list array of the policy.
The attribute evaluation function needs to be modified for that has been added to the utility module implemented in #16 .