|
Post by chaul on Dec 29, 2023 3:51:44 GMT
Hi, in the schema of Chassis/PhysicalSecurity/IntrusionSensor, it says
"longDescription": "This property shall contain the physical security state of the chassis. If the IntrusionSensorReArm property contains `Manual`, a client may set this property to `Normal` to reset the physical security state."
And in IntrusionSensorReArm:
"enumLongDescriptions": {
"Automatic": "This value shall indicate the service sets the IntrusionSensor property to `Normal` when no security condition is detected.",
"Manual": "This value shall indicate a user is required to set the IntrusionSensor property to `Normal` to restore the sensor to its normal state."
},
I wonder if there's any special action expected when user write "HardwareIntrusion" to IntrusionSensor? It's obvious that the sensor will be updated immediately to the state of the hardware. Should @allowablevalues of IntrusionSensor be Normal to restrict user from setting other value to it?
Thank you.
|
|
|
Post by mraineri on Dec 29, 2023 13:59:58 GMT
Based on the long description for IntrusionSensor, a client is only allowed to use "Normal" in PATCH requests; the service can internally set the property to other values based on the state of the sensor, but I would expect every service today to reject client requests that contain either "HardwareIntrusion" or "TamperingDetected". It might be worth us to call that out explicitly in the description though; I'll raise this to discuss with others.
You can certainly use the allowable values annotation to further convey this to clients; that's perfectly legal, but might be unnecessary given the schema descriptions.
|
|
|
Post by chaul on Jan 2, 2024 2:43:54 GMT
I'm implementing some codes and want to clarify. Got it. Thank you a lot for your response.
|
|