Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Juniper Mist AI 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

Juniper Mist AI Orgs NAC Tags API is one of 211 APIs that Juniper Mist AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Orgs NAC Tags. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 2 paths, and defines 20 schemas. It is described by OpenAPI 3.1.0, at version 2604.1.1.

Requests are made against 12 base URLs: https://api.mist.com, https://api.gc1.mist.com, https://api.ac2.mist.com, https://api.gc2.mist.com, https://api.gc4.mist.com, https://api.eu.mist.com, https://api.gc3.mist.com, https://api.ac6.mist.com, https://api.gc6.mist.com, https://api.ac5.mist.com, https://api.gc5.mist.com, https://api.gc7.mist.com.

5 operations 2 paths 20 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2604.1.1
Base URL
https://api.mist.com/api/v1
Authentication
API Key, HTTP Basic, API Key
License
Resource Areas
1

Authentication & Security 3

Juniper Mist AI Orgs NAC Tags API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (apiToken). It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as X-CSRFToken (csrfToken). By default, every request must be authenticated.

  • apiToken — Like many other API providers, it’s also possible to generate API Tokens to be used (in HTTP Header) for authentication. An API token ties to a Admin with equa…
  • basicAuth — While our current UI uses Session / Cookie-based authentication, it’s also possible to do Basic Auth.
  • csrfToken — This protects the website against [Cross Site Request Forgery](https://en.wikipedia.org/wiki/Cross-siterequestforgery), all the POST / PUT / DELETE APIs needs…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Orgs NAC Tags 5

NAC Tags are the building blocks to compose nacrules. They can either appear in the "matching" / "notmatching" sections of a nacrule, in which case they play the role of classifie…

GET
/api/v1/orgs/{org_id}/nactags
listOrgNacTags
listOrgNacTags 6 params → 200400401403404429
POST
/api/v1/orgs/{org_id}/nactags
createOrgNacTag
createOrgNacTag 1 param body → 200400401403404429
DELETE
/api/v1/orgs/{org_id}/nactags/{nactag_id}
deleteOrgNacTag
deleteOrgNacTag 2 params → 200400401403404429
GET
/api/v1/orgs/{org_id}/nactags/{nactag_id}
getOrgNacTag
getOrgNacTag 2 params → 200400401403404429
PUT
/api/v1/orgs/{org_id}/nactags/{nactag_id}
updateOrgNacTag
updateOrgNacTag 2 params body → 200400401403404429

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are nac_tag (19 properties), response_http404 (1 property), response_http400 (1 property), response_http401 (1 property). Each schema is shown below with its type and property counts.

nac_tag_values
array
If type==match
nac_tag_username_attr
string
enum: automatic, cn, dns, email, upn
nac_tag_radius_vendor_attrs
array
If type==radiusvendorattrs, user can specify a list of one or more vendor-specific attributes in the field "radiusvendorattrs". It is the responsibility of the…
id
string
Unique ID of the object instance in the Mist Organization
nac_tag_type
string
enum: egressvlannames, gbptag, match, radiusattrs, radiusgroup, radiusvendorattrs, redirectnacportalid, sessiontimeout, usernameattr, vlan
response_http403
object
1 property
nac_tag_egress_vlan_names
array
If type==egressvlannames, list of egress vlans to return
nac_tag_match
string
if type==match. enum: certcn, certeku, certissuer, certsan, certserial, certsub, certtemplate, clientmac, edrstatus, gbptag, hostname, idprole, ingressvlan, md…
redirect_nacportal_id
string
If type==redirectnacportalid, the ID of the NAC portal to redirect to
nac_tag
object
19 properties 2 required
response_http404
object
1 property
modified_time
number
When the object has been modified for the last time, in epoch
nac_tag_gbp_tag
If type==gbptag
response_http400
object
1 property
response_http429
object
1 property
nac_tags
array
response_http401
object
1 property
nac_tag_radius_attrs
array
If type==radiusattrs, user can specify a list of one or more standard attributes in the field "radiusattrs". It is the responsibility of the user to provide a…
org_id
string
created_time
number
When the object has been created, in epoch

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mist-ai-orgs-nac-tags-api-openapi.yml Raw ↑

Other APIs Juniper Mist AI publishes across the network.

Juniper Mist WebSocket Streaming API
Juniper Mist Webhooks API
Juniper Mist AI Admins API
Juniper Mist AI Admins Login API
Juniper Mist AI Admins Login - OAuth2 API
Juniper Mist AI Admins Logout API
Juniper Mist AI Admins Lookup API
Juniper Mist AI Admins Recover Password API
Juniper Mist AI Constants Definitions API
Juniper Mist AI Constants Events API
Juniper Mist AI Constants Models API
Juniper Mist AI Installer API