IETF NETCONF (Network Configuration) Working Group WG Web: <https://datatracker.ietf.org/wg/netconf/> WG List: <mailto:netconf@ietf.org> Author: Andy Bierman <mailto:andy@yumaworks.com> Author: Martin Bjorklund <mailto:mbj@tail-f.com> Network Configuration Access Control Model. Copyright (c) 2012 - 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 8341; see the RFC itself for full legal notices. Added support for YANG 1.1 actions and notifications tied to data nodes. Clarified how NACM extensions can be used by other data models. RFC 8341: Network Configuration Access Control Model Initial version. RFC 6536: Network Configuration Protocol (NETCONF) Access Control Model Used to indicate that the data model node represents a sensitive security system parameter. If present, the NETCONF server will only allow the designated 'recovery session' to have write access to the node. An explicit access control rule is required for all other users. If the NACM module is used, then it must be enabled (i.e., /nacm/enable-nacm object equals 'true'), or this extension is ignored. The 'default-deny-write' extension MAY appear within a data definition statement. It is ignored otherwise. Used to indicate that the data model node controls a very sensitive security system parameter. If present, the NETCONF server will only allow the designated 'recovery session' to have read, write, or execute access to the node. An explicit access control rule is required for all other users. If the NACM module is used, then it must be enabled (i.e., /nacm/enable-nacm object equals 'true'), or this extension is ignored. The 'default-deny-all' extension MAY appear within a data definition statement, 'rpc' statement, or 'notification' statement. It is ignored otherwise. General-purpose username string. The string containing a single asterisk '*' is used to conceptually represent all possible values for the particular leaf using this data type. Any protocol operation that creates a new data node. Any protocol operation or notification that returns the value of a data node. Any protocol operation that alters an existing data node. Any protocol operation that removes a data node. Execution access to the specified protocol operation. Access operation. Name of administrative group to which users can be assigned. Requested action is permitted. Requested action is denied. Action taken by the server when a particular rule matches. Path expression used to represent a special data node, action, or notification instance-identifier string. A node-instance-identifier value is an unrestricted YANG instance-identifier expression. All the same rules as an instance-identifier apply, except that predicates for keys are optional. If a key predicate is missing, then the node-instance-identifier represents all possible server instances for that key. This XML Path Language (XPath) expression is evaluated in the following context: o The set of namespace declarations are those in scope on the leaf element where this type is used. o The set of variable bindings contains one variable, 'USER', which contains the name of the user of the current session. o The function library is the core function library, but note that due to the syntax restrictions of an instance-identifier, no functions are allowed. o The context node is the root node in the data tree. The accessible tree includes actions and notifications tied to data nodes. Parameters for NETCONF access control model. Enables or disables all NETCONF access control enforcement. If 'true', then enforcement is enabled. If 'false', then enforcement is disabled. Controls whether read access is granted if no appropriate rule is found for a particular read request. Controls whether create, update, or delete access is granted if no appropriate rule is found for a particular write request. Controls whether exec access is granted if no appropriate rule is found for a particular protocol operation request. Controls whether the server uses the groups reported by the NETCONF transport layer when it assigns the user to a set of NACM groups. If this leaf has the value 'false', any group names reported by the transport layer are ignored by the server. Number of times since the server last restarted that a protocol operation request was denied. Number of times since the server last restarted that a protocol operation request to alter a configuration datastore was denied. Number of times since the server last restarted that a notification was dropped for a subscription because access to the event type was denied. NETCONF access control groups. One NACM group entry. This list will only contain configured entries, not any entries learned from any transport protocols. Group name associated with this entry. Each entry identifies the username of a member of the group associated with this entry. An ordered collection of access control rules. Arbitrary name assigned to the rule-list. List of administrative groups that will be assigned the associated access rights defined by the 'rule' list. The string '*' indicates that all groups apply to the entry. One access control rule. Rules are processed in user-defined order until a match is found. A rule matches if 'module-name', 'rule-type', and 'access-operations' match the request. If a rule matches, the 'action' leaf determines whether or not access is granted. Arbitrary name assigned to the rule. Name of the module associated with this rule. This leaf matches if it has the value '*' or if the object being accessed is defined in the module with the specified module name. This choice matches if all leafs present in the rule match the request. If no leafs are present, the choice matches all requests. This leaf matches if it has the value '*' or if its value equals the requested protocol operation name. This leaf matches if it has the value '*' or if its value equals the requested notification name. Data node instance-identifier associated with the data node, action, or notification controlled by this rule. Configuration data or state data instance-identifiers start with a top-level data node. A complete instance-identifier is required for this type of path value. The special value '/' refers to all possible datastore contents. Access operations associated with this rule. This leaf matches if it has the value '*' or if the bit corresponding to the requested operation is set. The access control action associated with the rule. If a rule has been determined to match a particular request, then this object is used to determine whether to permit or deny the request. A textual description of the access rule.