Hi guys,
I'm having a similar problem.
I don't know if I'm understanding it wrong, but somethings in the Iotivity
implementation appear to be incongruous with the OCF specs.
Using roles is one of them.
Another one of this incongruities was also pointed out by Filipe in the
email "Question about discoverable resources", the OCF specs says that "For
secure discovery, any Resource that has an associated ACL2 will be listed
in the response to /oic/res Resource *if and only if *the Client has
permissions to perform at least one of the CRUDN operations " but when we
tried to do so, clients with no permissions were able to discover secure
resources.
I'm starting to feel a little lost.
Best regards,
Eduardo Maia
2018-02-01 18:45 GMT-02:00 Filipe de Melo Silva <f...@cin.ufpe.br>:
> Hi,
>
> Maybe you guys can help me with something. I'm working in a sample of
> ownership transfer. The ownership transfer is working well and now I want
> to restrict the resource access to owner device. By looking at the OCF
> specifications, I discovered something like to add this fields in the ACE:
>
> "subject": { "authority": "owner", "role": "owner" }
>
> However, when I put it in the json, the *json2cbor* tool is not working,
> raising the following error:
>
> Found 'aclist2' tag... resource is oic.r.acl2 type.
> OUT JSONToAclBin: failure
>
> The complete ACE:
> {
> "aceid": 5,
> "subject": { "authority": "owner", "role": "owner" },
> "resources": [
> { "href": "/oic/led/0" }
> ],
> "permission": 14
> }
>
> am I doing this by the wrong way?
>
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev@lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
