Thanks, I'll give this a shot, -Todd From: Daniel Mihai [mailto:daniel.mi...@microsoft.com] Sent: Tuesday, January 31, 2017 4:38 PM To: Morrow, Joseph L <joseph.l.morrow at intel.com>; Malsbary, Todd <todd.malsbary at intel.com>; iotivity-dev at lists.iotivity.org Subject: RE: Default .dat file
I agree with Joey. However, if you: 1. Pick up today's change from https://gerrit.iotivity.org/gerrit/#/c/13569/, and 2. Your app/device has a functional Random PIN callback (as the sample sampleserver_randompin app does) Then provisioningclient option 11 followed by 20 should be able to Onboard your app. In case it still doesn't work, please let me know and/or log a bug in JIRA. Dan From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Morrow, Joseph L Sent: Tuesday, January 31, 2017 4:33 PM To: Malsbary, Todd <todd.malsbary at intel.com<mailto:todd.malsbary at intel.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Default .dat file Hi Todd, The expected scenario may be that the auto-generated *.dat file works with the provisioningclient app. However, I have not seen this work. What works for me is taking the oic_svr_db_client.dat at <iotivity>/resource/csdk/security/provisioning/sample and place that were the autogenerated one gets created. The provisioningclient app works then. I look forward to hear why the autogenerated version doesn't work the same. Thanks, Joey Morrow From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Malsbary, Todd Sent: Tuesday, January 31, 2017 4:23 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Default .dat file Hello, When I create a server app and register the persistent storage handlers, a .dat file is created for me when one does not already exist. I then use the provisioningclient app to attempt ownership transfer but it fails. I believe this is due to missing acls for /oic/sec/doxm in the created .dat file. Is this the expected behavior? Am I missing any additional APIs to setup the .dat file suitable for ownership transfer and provisioning? Thanks, -Todd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170201/427ec589/attachment.html>
