Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create or modify NACM data node access rule with path using JSON encoding #129

Closed
olofhagsand opened this issue Aug 21, 2020 · 0 comments
Labels

Comments

@olofhagsand
Copy link
Member

If you want to modify NACM RFC8341 data node paths dynamically (ie not only given at startup time), you cannot do this using JSON encoding. The reason is that paths use instance-identifiers which need a namespace context which are not given by JSON.
XML encoding works fine.
Example using XML encoding:

     <rule-list>
       <name>guest-acl</name>
       <group>guest</group>
       <rule>
         <name>deny-nacm</name>
         <path xmlns:n="urn:ietf:params:xml:ns:yang:ietf-netconf-acm">   
           /n:nacm   <<<-----------
         </path>
olofhagsand added a commit that referenced this issue Aug 30, 2020
…using JSON encoding #129](#129). The evaluation of NACM datanode rule path is assumed to be canonical namespace and cannot be overruled with `xmlns` rules.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant