Thanks Tonny, Yes, IoTivity 1.3 requires the /acl2 Resource and proper formatting using the ACE2 definition. Tthe /acl resource is deprecated and cannot be used in OCF 1.0 Devices.
To get the equivalent function to the “*” Subject (all Subjects) in ACE1, you just need to create two ACE2 entries, with “auth_crypt” and “anon_clear” Subject, which will encompass all Subjects. Let me know if you need help with the .json file example of this config! Thanks, Nathan From: [email protected] [mailto:[email protected]] On Behalf Of Tonny Tzeng Sent: Tuesday, August 15, 2017 9:21 AM To: iotivity-dev <[email protected]> Subject: [dev] provisioning client discover no unowned devices with V2 ACL Hi developers, I tried to supply my sampleserver_justworks app with a modified oic_svr_db_server_justworks.json, as I'd like to defines ACL in V1 format, instead of using the original V2 ACLs, but the provisioning client can't discover this unowned device anymore if the device uses V1 ACL. Is it right behavior or any restrictions when to use V1 ACLs? it looks to me the V1 ACL accepts "*" uuid, and I am hesitated to use the connection type ACE in V2, so I'm wondering why the use of V1 ACL causing the unowned device becomes undiscoverable? Best Regards, Tonny
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
