How to push meta data name-value pairs to an endpoint via API

[SamuelFullman6827]

I have already discovered that I can use CURL calls via the ers API, and, for example:

• Add an endpoint
• Add an endpoint to an identity group
• Get all endpoints in an identity group

I realize that an endpoint (defined by a MAC address) begins to "live" as the device comes online on the network, and a lot of information is stored about it and its habits.

My question, however, is, is there any way to push and permanently meta data or name-value pairs like "batch=17284" or "justification=John Smith" etc. as part of adding the endpoint, and also to retrieve this meta data when I get a list of endpoints, say in an identity group?  Thanks for your assistance.

[Damien Miller · Accepted solution]

You can map these to custom endpoint attributes which you define here.
https://<ise-node-ip>/admin/#administration/administration_identitymanagement/administration_identitymanagement_generalsettings/endpointCusAttrs


<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<ns4:endpoint description="test endpoint" id="6bb8e710-26a5-11e9-906f-665f6f9a1390" name="10:10:10:20:20:20" xmlns:ers="ers.ise.cisco.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns4="identity.ers.ise.cisco.com">
<link rel="self" href="https://10.0.0.101:9060/ers/config/endpoint/name/10:10:10:20:20:20" type="application/xml"/>
<customAttributes>
<customAttributes>
<entry>
<key>Batch</key>
<value>456789</value>
</entry>
<entry>
<key>Justification</key>
<value>John Doe</value>
</entry>
</customAttributes>
</customAttributes>
<groupId>aa0e8b20-8bff-11e6-996c-525400b48521</groupId>
<identityStore></identityStore>
<identityStoreId></identityStoreId>
<mac>10:10:10:20:20:20</mac>
<portalUser></portalUser>
<profileId></profileId>
<staticGroupAssignment>false</staticGroupAssignment>
<staticProfileAssignment>false</staticProfileAssignment>
</ns4:endpoint>

[SamuelFullman6827]

@Damien, I notice that you have <customAttributes> nested inside another <customAttributes> tag. Is this correct and what is the reason for this? thanks.

[Damien Miller]

I pulled that straight from the API with no editing. I am not sure why other than it was.