I have been using the ERS API's for some time now, but with the introduction of ISE 2.0, i am starting to get some alarms in ISE, that state that my requests are using out dated information. I am assuming it has something to do with the content-type setting, but i am not sure.
Alarm:
<181>Feb 4 23:18:24 ise CISE_Administrative_and_Operational_Audit 0000000461 1 0 2016-02-04 23:18:24.964 +01:00 0000011627 60504 NOTICE ERS: ERS request content-type header is out-dated, ConfigVersionId=62,
This requests to get the version info for the endpoint functions triggers no errors and returns ok data :
curl -k -H "ACCEPT: application/vnd.com.cisco.ise.identity.endpoint.1.0+xml" https://user:pass@1.2.3.4:9060/ers/config/endpoint/versioninfo
<?xml version="1.0" encoding="utf-8" standalone="yes"?><ns3:versionInfo xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns3="ers.ise.cisco.com"><currentServerVersion>1.0</currentServerVersion><link rel="self" href="https://1.2.3.4:9060/ers/config/endpoint/versioninfo" type="application/xml"/><supportedVersions>1.0</supportedVersions></ns3:versionInfo>
When i then use the "version 1.0" info in my accept header in a search for a specific mac address in the endpoint list, i get the alarm, but i still get ok data returned
curl -k -H "ACCEPT: application/vnd.com.cisco.ise.identity.endpoint.1.0+xml" https://user:pass@1.2.3.4:9060/ers/config/endpoint?filter=mac.EQ.11:22:33:44:55:66
So i try to add a content-type header
curl -k -H "ACCEPT: application/vnd.com.cisco.ise.identity.endpoint.1.0+xml" -H "Content-Type:
application/vnd.com.cisco.ise.identity.endpoint.1.0+xml" https://user:pass@1.2.3.4:9060/ers/config/endpoint?filter=mac.EQ.11:22:33:44:55:66
Same result, an alarm is triggered and i get ok data back.
Am i missing something really obvious ?
