Juniper Networks Orgs NAC Tags API
NAC Tags are the building blocks to compose nacrules. They can either appear in the "matching" / "not_matching" sections of a nacrule, in which case they play the role of classifiers, or they could appear in the "apply_tags" section of the of a nacrule, in which case they influence the result. When the "type" field of nactag is "match", it can be used as the classifier of a nacrule. - "match" field specifies the attribute name and "values" field specifies the list of attribute values to match on. - When multiple values are specified, its treated as an OR condition between those values. This behavior can be changed by setting "match_all" field to "true", in which case it is treated as an AND condition between those values. - By default, exact match is performed. This behavior can be changed as follows: - Adding `-` at the beginning will perform suffix match (ex: -staff will match foo-staff and bar-staff) - Adding `-` at the end will perform prefix match (ex: foo- will match foo-staff and foo-interns) - Adding `!` at both ends will perform substring match (ex: printer will match hp-printer-bldg1, brother-printer-lab) - Adding `!` at the beginning will perform negation of the match (ex: !ssid-guest will match any string that is not ssid-guest) - Note: when negation should be used along with suffix/substring operation, ! should always precede \* (ex: !guest will match any string that is not ending with guest) When the "type" field of nactag is NOT "match", it can be used as the result of a nacrule. "type" field identifies the action to take and the corresponding field would provide any associated parameters to that action. When the "type" field of nactag is NOT "match" and is any of the result type also supported by usermac table(`vlan`), "allow_usermac_override" field can be set to true to allow the override by usermac result