Hi Kyle, The AMS as implemented in IoTivity is only a partial implementation of an optional feature, and is slated for removal in the next release, because we felt it was confusing. It's also mostly untested and was meant as a reference beginning point but never was completed, the original developer having since moved on.
The AMS service is documented in the OIC/OCF Security Spec v1.1, and otherwise, there is no other documentation available for that feature. This is another reason we felt it would be best to remove the code. Thanks, Nathan Heldt-Sheller OSWG SC_TG Security TF Chair -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Haefner,Kyle Sent: Wednesday, May 25, 2016 7:38 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] AMS Hi All, I'm looking for more information on the Access Management Service and I can't seem to find where it might be documented. Specifically, I'm looking at: How it is populated? How responses are encrypted/signed? Is there a hierarchical structure to them, i.e. if a resource is not found in one can a server request it from another? Is there a difference on how a server requests an ACL from a local AMS vs a remote/cloud based one? Thanks for any help you can provide. Kyle Kyle Haefner, M.S. Communication Systems Programmer Colorado State University Fort Collins, CO Phone: 970-491-1012 Email: kyle.haefner at colostate.edu SIP: kyle.haefner at colostate.edu _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
