Hello, > (while building we have replaced 'tinycbor' in iotivity constrained from >the > tinycbor folder of iotivity1.2.0).
Whats this step? It shouldn?t be necessary. > We are start simpleserver in iotivity-constrained (its starting with >random uuid ) > and its discovered and registered by provisioningclient with of >iotivity 1.2.0. Are you running simpleserver from the samples without modification? If so, the samples expect that you create a directory called ?creds? under the current path (Under port/linux/ for eg. if you?re running simpleserver from there) so that the framework can persist the credentials, ACLs and provisioning state. If you haven?t done that, then nothing is persisted and of course it starts fresh the next time its run. Lastly, please ensure that you?re aware of all the provisioning steps, i.e. you would need to 1) assume ownership of simpleserver, 2) provision pairwise (128-bit) credentials, and 3) provision an ACL for /a/light. Only then will you be able to use simpleclient to access /a/light on simpleserver over DTLS. - Kishen Maloor Intel Open Source Technology Center From: <iotivity-dev-boun...@lists.iotivity.org> on behalf of JOTIRLING SWAMI <swamijotirlingj at gmail.com> Date: Tuesday, November 22, 2016 at 10:35 PM To: "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org>, "heldt-sheller at intel.com" <heldt-sheller at intel.com>, "randeep.s at samsung.com" <randeep.s at samsung.com> Subject: [dev] Issue in iotivity-constrained (Generating Random uuid ) Hi All, We are working on iotivity-Constrained Security, we have build iotivity-constrained for linux (Raspaberry-Pi) using "make SECURE=1 DEBUG=1" its building successfully (while building we have replaced 'tinycbor' in iotivity constrained from the tinycbor folder of iotivity1.2.0). We are start simpleserver in iotivity-constrained (its starting with random uuid ) and its discovered and registered by provisioningclient with of iotivity 1.2.0. when we restart the iotivity-constrained simpleserver it again generates new random uuid and its becoming unowned to previously owned provisioningclient. Regards, Jotirling Swami,
