local_policy

Device Configuration Policy

Device Configuration Policy is needed because it is really easy to set up an unauthorized wifi network. Small plug-in and play devices can act as access points. While devices like smartphones and tablets can act as wifi hotspots. So, any user can connect to any access point or hotspot and get access to a network. This can unusually attract a lot of threats. Therefore, it is necessary to have a proper device policy so that not any device can act as an access point or wifi hotspot.

JSON Table

Parameter Data Type Description
policyCreatedAtLocId application/json ID of the location at which the policy has been defined. For details
about the JSON, click Location
ID.
policyType String A read-only field for internal use.
defaultTemplateId int ID of the default template for a given location.
applyToExistingDevices boolean A true or false value indicating whether the existing devices are using
the new default policy template. While saving the policy, set this field
to true to ensure that all existing devices use the default policy template.

Copy Sample JSON
Sample JSON 
{
    "policyCreatedAtLocId": {
        "type": "locallocationid",
        "id": 0
    },
    "policyType": "DEVICE_CONFIG",
    "defaultTemplateId": -1,
    "applyToExistingDevices": false
}
API Calls
Get

/V5/policies/deviceconfig/{fetch_factory_default}

Put

/V5/policies/deviceconfig

Put

<Base_URL>/V2/analytics/associationdata/{startdate}/{enddate}

Post

/V5/policies/deviceconfig

Delete

/V5/policies/deviceconfig

Get Device Configuration Policy

Description This API is used to fetch the Device Configuration Policy at a specified location
from Wireless Manager or Arista Cloud Services.
Users with the roles can call this API: superuser, administrator, operator, and viewer.
Syntax
Get <Base_URL>/policies/deviceconfig/{fetch_factory_default}?
locationid=<value>&nodeid=<value>

Here,

  • locationid

    It is an integer value specifying the location for which the Device Configuration Policy
    is fetched. To retrieve the value for location id refer Location call.

  • nodeid

    It is an integer value specifying the node in a server cluster setup.

  • fetch_factory_default

    Is a boolean value specifying whether factory default policies will be fetched
    or user-defined policies. If set to true the factory default policies are fetched,
    and if set to false user-defined policies are fetched.
Sample code
Get https://training.mojonetworks.com/new/webservice/V5/policies/
deviceconfig/true?locationid=0
Request Body This API call does not require any request body parameters.
Response Body If the API call is successful, the HTTP response status is 200.
The response body contains the details of Device Configuration Policy. The response is in the application/json format.

Customize Device Configuration Policy

Description This API is used to customize the Device Configuration Policy at a specified location in
Wireless Manager or Arista Cloud Services. After calling this API, the policy
can be modified by calling the Modify Device Configuration Policy API at
the specified location.
Users with the roles can call this API: superuser, administrator, operator, and viewer.
Syntax
PUT <Base_URL>/policies/deviceconfig?locationid=<value>&nodeid=<value>

Here,

  • locationid

    It is an integer value specifying the location for which the Device Configuration Policy
    is customized. To retrieve the value for location id refer Location call.

  • nodeid

    It is an integer value specifying the node in a server cluster setup.
Sample code
PUT https://training.mojonetworks.com/new/webservice/V5/policies/
deviceconfig?locationid=1
Request Body This API call does not require any request body parameters.
Response Body If the API call is successful, the HTTP response status is 204.
The response body does not contain any information.

Put APIs

Description This API is used to fetch the APs that match the specified filter criteria from the allowed locations for the logged-in user. If no filters are specified, all the APs from the allowed locations are fetched. However, this API is not supported in a server cluster environment.

Note: Do not use this API to fetch more than 100 devices. For fetching larger number of devices, consider using the Get Paged List of APs API.
User Privileges Users with the following roles can call this API: superuser, administrator, and operator.

Request Body Parameters
This API call does not require any request body parameters.

Response Body
If the API call is successful, the HTTP response status is 200. The response body contains the details of the APs that match the filter criteria. The response is in the application/json format. Click AP to view the complete detais of the JSON along with a sample output.

Error codes
If the API call is successful, the HTTP response status is 200.
Syntax
GET /devices/aps
Sample code
GET https://training.mojonetworks.com/new/webservice/v2/devices/aps
GET
https://training.mojonetworks.com/new/webservice/v2/devices/aps?macaddress=00:11:74:33:23:12&macaddress=00:11:74:45:12:21
GET
https://training.mojonetworks.com/new/webservice/v2/devices/aps?capability=49&locationid=10&locationid=12&sortcolumn=devicename&sortascending=false
URL Parameters This API call takes optional URL parameters to filter the list of APs to be fetched and the column on which the output must be sorted. AP Filter Parameters lists the parmeter names, datatypes, applicable values, and whether the results can be sorted based on the parameter.
Query Parameters This API call takes optional URL parameters to filter the list of APs to be fetched and the column on which the output must be sorted. AP Filter Parameters lists the parmeter names, datatypes, applicable values, and whether the results can be sorted based on the parameter.
Response Body If the API call is successful, the HTTP response status is 200. The response body contains the details of the APs that match the filter criteria. The response is in the application/json format. Click AP to view the complete detais of the JSON along with a sample output.

Modify Device Configuration Policy

Description This API is used to modify Device Configuration Policy at a specified location
in Wireless Manager or Arista Cloud Services. Before calling this API, the
policy must be customized by calling the Customize Device Configuration Policy
API at the specified location.
Users with the roles can call this API:superuser, administrator, operator, and viewer.
Syntax
POST <Base_URL>/policies/deviceconfig?locationid=<value>&nodeid=<value>

Here,

  • locationid

    It is an integer value specifying the location for which the Device Configuration Policy
    is modified. To retrieve the value for location id refer Location call.

  • nodeid

    It is an integer value specifying the node in a server cluster setup.
Sample code
POST https://training.mojonetworks.com/new/webservice/V5/policies/
deviceconfig?locationid=2
Request Body This API call requires the modified details of the Device Configuration Policy,
which are passed as parameters in the request body. The parameters are passed in
the application/json format. You must provide the appropriate values for
the following mandatory JSON attributes.

  • policyCreatedAtLocId
  • policyCreatedAtLocId/type
  • policyCreatedAtLocId/id

A sample request will have a structure as follows:

{
...
List of Device Configuration Policy with the mandatory attributes mentioned above
...
}
Response Body If the API call is successful, the HTTP response status is 204.
The response body does not contain any information.

Inherit Device Configuration Policy

Description This API is used to inherit Device Configuration Policy at a specified location
from its parent location in the Mojo Server or the Arista Cloud Services. The
Device Configuration Policy, by default, is inherited from the parent location. This
API can be called to inherit the policy from the parent location if the
Customize Device Configuration Policy API was called at a specified
location earlier. On calling this API, the customized Device Configuration Policy is
deleted and the policy defined on the parent location is inherited.
Users with the roles can call this API: superuser, administrator, operator and viewer.
Syntax
DELETE <Base_URL>/policies/deviceconfig?locationid=<value>
&nodeid=<value>

Here,

  • locationid

    It is an integer value specifying the location for which the
    Device Configuration Policy is inherited. To retrieve the value for location id refer Location call.

  • nodeid

    It is an integer value specifying the node in a server cluster setup.
Sample code
DELETE
https://training.mojonetworks.com/new/webservice/V5/policies/deviceconfig?
locationid=2
Request Body This API call does not require any request body parameters.
Response Body If the API call is successful, the HTTP response status is 204.
The response body does not contain any information.

Test APIs

Description This API is used to fetch the APs that match the specified filter criteria from the allowed locations for the logged-in user. If no filters are specified, all the APs from the allowed locations are fetched. However, this API is not supported in a server cluster environment.

Note: Do not use this API to fetch more than 100 devices. For fetching larger number of devices, consider using the Get Paged List of APs API.
User Privileges Users with the following roles can call this API: superuser, administrator, and operator.

Request Body Parameters
This API call does not require any request body parameters.

Response Body
If the API call is successful, the HTTP response status is 200. The response body contains the details of the APs that match the filter criteria. The response is in the application/json format. Click AP to view the complete detais of the JSON along with a sample output.

Error codes
If the API call is successful, the HTTP response status is 200.
Syntax
GET /devices/aps
Sample code
GET https://training.mojonetworks.com/new/webservice/v2/devices/aps
GET
https://training.mojonetworks.com/new/webservice/v2/devices/aps?macaddress=00:11:74:33:23:12&macaddress=00:11:74:45:12:21
GET
https://training.mojonetworks.com/new/webservice/v2/devices/aps?capability=49&locationid=10&locationid=12&sortcolumn=devicename&sortascending=false
URL Parameters This API call takes optional URL parameters to filter the list of APs to be fetched and the column on which the output must be sorted. AP Filter Parameters lists the parmeter names, datatypes, applicable values, and whether the results can be sorted based on the parameter.
Query Parameters This API call takes optional URL parameters to filter the list of APs to be fetched and the column on which the output must be sorted. AP Filter Parameters lists the parmeter names, datatypes, applicable values, and whether the results can be sorted based on the parameter.
Response Body If the API call is successful, the HTTP response status is 200. The response body contains the details of the APs that match the filter criteria. The response is in the application/json format. Click AP to view the complete detais of the JSON along with a sample output.