Hi Markus, Thanks for committing to log the issue in JIRA.
It should take a couple of minutes for anyone (especially the associated developers) to reproduce based on my e-mail, unless I missed some steps, in which case someone can let us know. FYI simpleclient and simpleserver are able to communicate just fine over DTLS with the provided and preset .DAT files. They however fail the provisioning path in the absence of those files. If its just the case that the simpleclient/server need to be updated specially to support provisioning (which would further beg the question why?), or just need to be updated to comply with other recent modifications, it might be a simpler fix, or even just an e-mail to this list with pointers might do for the moment. If its however the case that the provisioning tools themselves need to be updated to comply with recent security model related changes, then the tools are indeed broken as I suggested, and its up to those in charge, but I would recommend that it be logged as a critical issue worthy of a fix since the ability to provision apps is the whole purpose of those tools. Thanks, -Kishen. - Kishen Maloor Intel Open Source Technology Center On 4/13/16, 4:40 PM, "Markus Jung" <markus.jung at samsung.com> wrote: >Hello Kishen, >thanks for reporting the issue I will document it in Jira and we will >investigate the problem. But as Nathan mentioned, it might be "only" a >problem with the sample app, which is definitely not good since it is the >first thing that new developers will have a look on. >We are aware that the documentation for IoTivity is currently in a poor >state. Uze Choi is leading now a TG for technical support which will also >address this issue. >Best regards >Markus >
