Provisioning Sample README updated

Patch #1: README file updated
Patch #3: CBOR change stated
Patch #4: File permission fixed

Change-Id: I04d7944aa720960777991277df94bdd9ac7018b1
Signed-off-by: Jongmin Choi <jminl.choi@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/7373
Reviewed-by: Jongsung Lee <js126.lee@samsung.com>
Reviewed-by: Yonggoo Kang <ygace.kang@samsung.com>
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Chul Lee <chuls.lee@samsung.com>
Reviewed-by: Randeep Singh <randeep.s@samsung.com>

diff --git a/resource/csdk/security/provisioning/sample/README-Provisioning-Tool.txt b/resource/csdk/security/provisioning/sample/README-Provisioning-Tool.txt
index 45d750f..d33178b 100644 (file)
--- a/resource/csdk/security/provisioning/sample/README-Provisioning-Tool.txt
+++ b/resource/csdk/security/provisioning/sample/README-Provisioning-Tool.txt
@@ -8,16 +8,24 @@ To execute Provisioning Tool sample:
 
 2) Verify Provisioning Tool functionality using secure sample apps:
 
-    On Resource Server Device which needs to be 'provisioned':
-       $ cd <iotivity-base>/out/<...>/release/resource/csdk/stack/samples/linux/secure
-       $ export LD_LIBRARY_PATH=<iotivity-base>/out/<...>/release
-       $ cp ../../../../security/provisioning/sample/oic_svr_db_unowned_server.json oic_svr_db_server.json
-       $ ./ocserverbasicops
+    Run Resource Server Device which needs to be 'provisioned':
+       $ ./sampleserver_justworks (Just Works)
+       or
+       $ ./sampleserver_randompin (Random Pin)
 
-
-    On Provisioning Tool Device:
-       $ cd <iotivity-base>/out/<...>/release/resource/csdk/security/provisioning/sample
+    Run Provisioning Tool Device:
        $ ./provisioningclient
 
     Follow the prompts on Provisioning Tool device and provisioning should be completed
-    successfully. You should see a message 'Provisioning Success~!!'.
+    successfully.
+
+    All security functionality operate using CBOR data (DAT files).
+    JSON files are for reference only as they are human-readable.
+    JSON files are not used by security-related functions.
+
+    If you wish to test functionality with data file different from the 
+    provided default DAT file, modify the JSON files 
+    (oic_svr_db_server_justworks.JSON, oic_svr_db_server_randompin.JSON)
+    and then use the JSON-to-CBOR conversion tool 
+    (<iotivity-base>/out/<...>/release/resource/csdk/security/tool/json2cbor)
+    to create a new DAT file.