current shadow service code always verify clientToken, while this is optional in shadow service about amazon-freertos HOT 4 CLOSED

Yes, as of now you need to put a client token in the shadow update document. As you correctly pointed out, it is optional in the AWS Shadow Service and we will see how we can make this optional in Amazon FreeRTOS.

Thank you for bringing it to our attention.

from amazon-freertos.

I understand the reason why Amazon FreeRTOS always expect ClientToken, this makes sure Shadow API get matching expectation/response from the cloud. The subscribed topic /update/accepted can receive a message whenever other updates take place.

I just found another issue, when an invalid json is updated and shadow service can't parse it, the response error document will not contain "clientToken", so the thing will not get rejected notification.
While if only some of field in JSON is not correct, (e.g. "state" -> "sta1e"), the response error document can include matching "clientToken" and Shadow API returns 400 soon.

Case 1:

Case 2:

from amazon-freertos.

This is by design as of now that we do not invoke any callback if the response document does not contain a valid clientToken. We will look into how can we inform the user about the receipt of a JSON document without a valid token.

Thank you for pointing it out.

from amazon-freertos.

Appreciate bringing this up, please don't hesitate to reach out again if any other concern. Closing this issue since it has been inactive.

from amazon-freertos.