Hi Nathan,

Thanks a lot for your help.
Actually, I did not keep the environment reproducing the issue (we switch
to POST from PU, for good reasons not related to the report).
I tried to reproduce the issue from scratch, and happily I was able to make
successful PUT requests with the ACLs behind the secure IoTivity.

*So I can confirm there is no generic issue with ACL support for PUT.*

I still don't know why it failed in  the original tests, but I guess its my
local that does not deserve the experts' time.

Regards,
Max

On Tue, Sep 12, 2017 at 10:34 PM, Heldt-Sheller, Nathan <
[email protected]> wrote:

> Hi Max,
>
>
>
> Looking at your log, it appears that a matching ACE is found which doesn’t
> contain the correct permissions… is there another ACE with the same
> conntype and Resource?
>
>
>
> Can you please send your entire /acl2 Resource (either print the Resource
> to the debug log just before the request, or send the .json for the entire
> .dat file you’re using)?
>
>
>
> Thanks,
> Nathan
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Max Kholmyansky
> *Sent:* Thursday, August 31, 2017 5:02 AM
> *To:* iotivity <[email protected]>
> *Subject:* [dev] PUT request fails with ACL using anon-clear access
>
>
>
> Hi
>
>
>
> Using IoTivity 1.3.0 (with some patches) - I have an issue to set ACL to
> allow PUT request with anon-clear access.
>
> Same works fine with GET and POST.
>
>
>
> Attaching the IoTivity traces.
>
>
>
> In my ACLs, I have a section:
>
> {
>     *"aceid"*: 5,
>     *"subject"*: { *"conntype"*: *"anon-clear" *},
>     *"resources"*: [
>         { *"href"*: *"/_br/c283934f-dfb4-391f-95de-ed1c161ab42e/mode" *}
>     ],
>     *"permission"*: 31
> }
>
> (same problem when using "*" instead of the specific URI)
>
>
> Yet in the logs I can see:
>
> ProcessAccessRequest:no ACL found matching conntype anon-clear for resource 
> /_br/c283934f-dfb4-391f-95de-ed1c161ab42e/mode
>
>
> Again, no issue with POST. Any hint how to make it work?
>
>
>
> Thanks
>
> Max
>
>
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to