NACM cleanup, uniform rule function, change of function names, etc.
This commit is contained in:
parent
8bf5cb0de5
commit
1e4022e73c
13 changed files with 180 additions and 247 deletions
15
CHANGELOG.md
15
CHANGELOG.md
|
|
@ -76,13 +76,16 @@
|
|||
* Note CLIXON_DATADIR (=/usr/local/share/clixon) need to be in the list
|
||||
* CLICON_YANG_MAIN_FILE Provides a filename with a single module filename.
|
||||
* CLICON_YANG_MAIN_DIR Provides a directory where all yang modules should be loaded.
|
||||
* NACM extension (RFC8341)
|
||||
* NACM Data node READ and WRITE access module support (RFC8341 3.4.5)
|
||||
* Access control points added for `get`, `get-config`, `edit-config` in addition to incoming rpc.
|
||||
* RFC 8341 Example A.2 implemented, see: [test/test_nacm_module.sh]
|
||||
* Remaining work: data-node PATH
|
||||
* NACM (RFC8341) experimental
|
||||
* Incoming RPC Message validation is supported (3.4.4)
|
||||
* Data Node Access validation is supported (3.4.5), except:
|
||||
* rule-type data-node path is not supported
|
||||
* Outgoing noitification aithorization is _not_ supported (3.4.6)
|
||||
* RPC:s are supported _except_:
|
||||
* `copy-config`for other src/target combinations than running/startup (3.2.6)
|
||||
* `commit` - NACM is applied to candidate and running operations only (3.2.8)
|
||||
* Client-side RPC:s are _not_ supported.
|
||||
* Recovery user "_nacm_recovery" added.
|
||||
* Example use is restconf PUT when NACM edit-config is permitted, then automatic commit and discard are permitted using recovery user.
|
||||
|
||||
### API changes on existing features (you may need to change your code)
|
||||
* Added `username` argument on `xmldb_put()` datastore function for NACM data-node write checks
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue