adoptACLDefault does not copy triples with acl:Authorization
See original GitHub issueI’m writing tests for the acl module, and noticed that adoptACLDefault does not copy the triples containing acl:Authorization into the new graph it builds. It seems that NSS does not care about this triples though, which is why the bug has gone unnoticed.
I’m creating this issue to verify my suspicion with others. If it is the case that NSS should require acl:Authorization triples, I’ll create a bug there as well.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
RFC 3530 NFS version 4 Protocol - IETF
The NFS version 4 protocol does not require a separate protocol to provide for the initial mapping between path name and filehandle. Instead...
Read more >Access Control: Policies, Models, and Mechanisms
Abstract. Access control is the process of mediating every request to resources and data maintained by a system and determining whether.
Read more >RFC 7530: Network File System (NFS) Version 4 Protocol
This error allows the server to notify the client that the security triple currently being used is not appropriate for access to the...
Read more >Access Control: Policies, Models, and ... - Springer Link
Abstract. Access control is the process of mediating every request to resources and data maintained by a system and determining whether.
Read more >Configuring Basic SNMP | Junos OS - Juniper Networks
By default, SNMP is not enabled. To enable SNMP, you must include the SNMP configuration statements at the [edit] hierarchy level. To configure...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I found the issue “Is acl:Authorization mandatory?” in the WAC spec, where the question is discussed as part of the new specification.
I’ll keep an eye out for those discussions, but until there’s a conclusion I’ll wait to create issues on NSS and the test-suite.
That being said, for the sake of semantics I suggest that we make sure that
acl:Authorizationis added as part of the code we touch in Solid UI and other places. (I’ve made sure to fix this in inadoptACLDefaultin a PR that is coming very soon.)Actually a triple bug, Solid UI + NSS + test-suite. 😃