Hello, I am implementing the OBT (OnBoarding Tool) functionality using IoTivity .
*My environment:* - IoTivity 1.2.1 (SECURE=1) - My app runs on Android, and uses Java API library. - To test the behavior, I use "sampleserver_justworks" running on Ubuntu Linux. I succeeded with locating of unowned device, and performing "ownership transfer" using JustWorks method. *However, if the device goes back to "Ready for OTM" state, I failed to perform the ownership transfer again with my app.* *Details:* - I perform ownership transfer - OK. - I simulate "Ready for OTM" by starting the sample with the original DAT file: it gives the same "di", but the device is uwowned "again". - My code locates the unowned device - OK. - When calling OcSecureResource.doOwnershipTransfer() on the returned unowned device - the callback gets never invoked (i.e. no notification on success / error). *The only workaround I found was to initialize the OBT with a new provisioning DB file*, using OcProvisioning.provisionInit() API. But I am afraid it's not a good option, since some data is lost. I understand there should be a way to perform the ownership transfer, despite same "di" was registered by the OBT in the past. Any hint will be appreciated. Best regards, Max Software Architect - SURE Universal Ltd. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170529/6864c9fe/attachment.html>
