Gregg, I can only talk to the spec, but I didn’t see anything in the spec that supported different “users” (aka other humans that have been provisioned mediator or client tokens by the “main” user) of the same device group to have different permissions. From the perspective of the device, all requests appear to come from the cloud, so if you need to handle finer granularity access control then it’d need to be a “not in the spec” feature in the cloud codebase (IIRC Samsung did this with their java implementation). I’m personally a CNCF fanboy so I’d recommend we check out OPA, but I don’t know what the priority or pre-existing strategy for implementing that feature is.
From: Gregg Reynolds [mailto:[email protected]] Sent: Thursday, August 9, 2018 11:45 AM To: Ondrej Tomcik <[email protected]> Cc: [email protected]; Scott King <[email protected]>; Max Kholmyansky ([email protected]) <[email protected]>; Jozef Kralik <[email protected]>; Peter Rafaj <[email protected]> Subject: Re: OCF Native Cloud 2.0 On Thu, Aug 9, 2018 at 6:48 AM, Ondrej Tomcik <[email protected]<mailto:[email protected]>> wrote: Dear IoTivity devs, Please be informed that the new Cloud 2.0 design concept is alive: https://wiki.iotivity.org/coapnativecloud Your comments are warmly welcome. Implementation is in progress. Obviously you put a lot of work into this, thanks. How does it handle third-party users? For example, Mom, Dad, kids, relatives, guests, all have different permissions, dynamically configurable. Gregg -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9840): https://lists.iotivity.org/g/iotivity-dev/message/9840 Mute This Topic: https://lists.iotivity.org/mt/24238274/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
