Hello IoTivity Dev, We've just merged a patch (https://gerrit.iotivity.org/gerrit/#/c/17993/) into IoTivity Master branch that implements the "dos" Property on the pstat Resource. This Property is mandatory as of OCF 1.0 and all OCF 1.0 devices must implement it.
The IoTivity security stack uses a cbor file to store persistent versions of the Security Virtual Resources (SVRs), of which pstat is one. Many of the sample apps use a pre-provisioned .dat file (e.g. "oic_svr_db_server.dat") which contains a pstat Resource representation (among others). With the addition of the mandatory "dos" Property, all of the sample .dat files (and thus, their corresponding .json files from which they are created) had to be updated to include "dos". I've done my best to find every .json SVR file, add the "dos" property in the appropriate state, and then re-generate the corresponding .dat file (using an updated json2cbor app that handles "dos"). However I may have missed some and I can't test all the sample apps. And of course I can't fix vendor apps that aren't part of IoTivity. TLDR; if your app suddenly stops working after pulling the latest master branch, please double-check your .json file contains the "dos" property, re-generate your .dat file (execute "json2cbor <my_file>.json <my_file>.dat"), and check your debug log for messages from the Security Resource Manager (filter on "OIC_SRM"). The resource/csdk/stack/samples/linux/secure/oic_svr_db_server.json file is a good example of a pre-provisioned SVR set that contains the "dos" Property; please refer to it (see the pstat Resource therein) if your app uses your own custom .json and .dat file. Thanks, Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/8b6c4ac9/attachment.html>
