On Dec 8, 2016 1:00 AM, "Max Kholmyansky" <max001 at gmail.com> wrote:
Hi *I would appreciate an advise why a server build with the "secure" IoTivity 1.2.1 library does not expose the device and platform information values set via APIs, when being queried via /oic/d and /oic/p* More details... Most of my app requirement are within the client OCF role, but there are some server requirements: it should support /oic/res, /oic/d, /oic/p, secure onboaridng and provisioning by another client. I am using Android SDK with IoTivity 1.2.1, and my code flow is as follows: - Init the OcPlatform in a mixed mode, i.e. ModeType.CLIENT_SERVER - Set the values to be exposed via /oic/d using OcPlatform.registerDevic eInfo - Set the values to be exposed via /oic/p using OcPlatform.registerPlatf ormInfo When working with a library built with SECURED=0, /oic/d and /oic/p respond as expected: all the values set by APIs are contained in the responses generated by the server. However, when working with a library built with SECURED=1 - the behavior is different: the servers responds to both /oic/d and /oic/p - but the response does not contain any of the values (for example, platform ID). fwiw this more evidence that SECURED=0 should not even be possible. gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161208/dbe98c6a/attachment.html>
