<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ERS JSON vs. XML POSTs in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541363#M528780</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am initially mocking it up in Postman (if you aren’t using this for REST testing you should).  Make sure you have your Content-Type and Accept headers set to either XML or JSON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The body I am using is exactly what I posted in my original post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on writing a C++ executable that uses libcurl to make REST calls to ISE.  I am working on a scenario for SCCM reimage processes where the customer could add my executable into the process and it would do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)     Find the MAC address of the primary interface on the system (Windows only).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)     Look up the MAC address in ISE to see if it exists.  If it exists grab the ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3)     Look up the endpoint identity group specified in ISE to make sure it exists and grab the ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4)     If the MAC address exists POST an update to ISE to statically assign the MAC address to the group ID found in #3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5)     If the MAC address doesn’t exist POST an creation to ISE to add in the MAC address and statically assign it to the group in #3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have my C++ code finished up through 3.  So now I am going to work on coding the POST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven’t coded in C++ for probably 15 years so I am hacking my way through it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Jun 2017 15:04:12 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2017-06-30T15:04:12Z</dc:date>
    <item>
      <title>ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541361#M528778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to create an Endpoint and assign it to a static group with ERS.&amp;nbsp; I have it working fine with XML:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" standalone="yes"?&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;ns3:endpoint xmlns:ns2="ers.ise.cisco.com" xmlns:ns3="identity.ers.ise.cisco.com"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;groupId&amp;gt;cabb7fc0-5d4d-11e7-b01c-024226b23b4f&amp;lt;/groupId&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;identityStore&amp;gt;&amp;lt;/identityStore&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;identityStoreId&amp;gt;&amp;lt;/identityStoreId&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;mac&amp;gt;11:22:33:44:55:66&amp;lt;/mac&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;portalUser&amp;gt;&amp;lt;/portalUser&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;profileId&amp;gt;aa0e8b20-8bff-11e6-996c-525400b48521&amp;lt;/profileId&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;staticGroupAssignment&amp;gt;true&amp;lt;/staticGroupAssignment&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;staticProfileAssignment&amp;gt;false&amp;lt;/staticProfileAssignment&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/ns3:endpoint&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to get it to work with JSON.&amp;nbsp; I thought I would just need to specify the same parameters as I did with XML:&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp; "ERSEndPoint" : {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "groupId" : "cabb7fc0-5d4d-11e7-b01c-024226b23b4f",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "identityStore" : "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "identityStoreId" : "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "mac" : "11:22:33:44:55:66",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "portalUser" : "",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "profileId" : "aa0e8b20-8bff-11e6-996c-525400b48521",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "staticGroupAssignment" : true,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "staticProfileAssignment" : false,&lt;/P&gt;&lt;P&gt;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am getting an error at the second to last bracket close and ISE says:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Invalid JSON Input: Unexpected character ('}' (code 125)): was expecting double-quote to start field name\n at [Source: java.io.StringReader@7c32de53; line: 11, column: 4]",&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does JSON require all the fields to be present?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 05:05:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541361#M528778</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-30T05:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541362#M528779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just yesterday I was trying to update the endpoint for a static group using XML but I was getting some error. Dint know that ISE supports JSON as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you share your complete POST request for the working XML requests ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 14:25:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541362#M528779</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2017-06-30T14:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541363#M528780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am initially mocking it up in Postman (if you aren’t using this for REST testing you should).  Make sure you have your Content-Type and Accept headers set to either XML or JSON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The body I am using is exactly what I posted in my original post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on writing a C++ executable that uses libcurl to make REST calls to ISE.  I am working on a scenario for SCCM reimage processes where the customer could add my executable into the process and it would do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)     Find the MAC address of the primary interface on the system (Windows only).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)     Look up the MAC address in ISE to see if it exists.  If it exists grab the ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3)     Look up the endpoint identity group specified in ISE to make sure it exists and grab the ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4)     If the MAC address exists POST an update to ISE to statically assign the MAC address to the group ID found in #3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5)     If the MAC address doesn’t exist POST an creation to ISE to add in the MAC address and statically assign it to the group in #3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have my C++ code finished up through 3.  So now I am going to work on coding the POST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven’t coded in C++ for probably 15 years so I am hacking my way through it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 15:04:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541363#M528780</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-30T15:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541364#M528782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also make sure that you are using a PUT when updating the Endpoint and a POST when creating one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 15:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541364#M528782</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-30T15:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541365#M528784</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I myself am building an API on top of ISE APIs in python.&lt;/P&gt;&lt;P&gt;Managed to write lot of functions but just started working on updating Identity Group yesterday&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 16:35:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541365#M528784</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2017-06-30T16:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541366#M528786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Utkarsh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the interest.&lt;/P&gt;&lt;P&gt;If your API is functional, tested and has good documentation on the purpose and how to use it, kindly share it in the community for others to benefit with caveats etc.&lt;/P&gt;&lt;P&gt;Python is widely used by a lot of people for writing API.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Krishnan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 17:33:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541366#M528786</guid>
      <dc:creator>kthiruve</dc:creator>
      <dc:date>2017-06-30T17:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541367#M528787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would have written mine in Python as well, but my program needs to be a self-contained DOS executable.  I think you can do that with Python, but it is easier with C++ and I have worked with C++ more recently than I have with Python (which is never).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got the PUT working with XML to update an endpoint:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;             sendData = ":9060/ers/config/endpoint/56b46ec0-5da2-11e7-b01c-024226b23b4f";&lt;/P&gt;&lt;P&gt;             curl_easy_setopt(curl, CURLOPT_URL, curl_url.c_str());&lt;/P&gt;&lt;P&gt;             curl_easy_setopt(curl, CURLOPT_HTTPHEADER, curl_headers);&lt;/P&gt;&lt;P&gt;             curl_easy_setopt(curl, CURLOPT_CUSTOMREQUEST, "PUT");&lt;/P&gt;&lt;P&gt;             curl_easy_setopt(curl, CURLOPT_POSTFIELDS, sendData.c_str());&lt;/P&gt;&lt;P&gt;             curl_result = curl_easy_perform(curl);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I have the update working with PUT now I just need to do a POST to create a new MAC address and assign it to the endpoint identity group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fun stuf!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 17:54:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541367#M528787</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-30T17:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541368#M528789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys if you have some examples I can post to the pages I have as well&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please post separate examples as docs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 18:02:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541368#M528789</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-06-30T18:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541369#M528790</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Were you able to make it work with Json ?&lt;/P&gt;&lt;P&gt;I just made it work with XML using REST client but in python JSON would make a better. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 18:48:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541369#M528790</guid>
      <dc:creator>umahar</dc:creator>
      <dc:date>2017-06-30T18:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541370#M528791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No I haven’t gotten JSON PUTs or POSTs to work yet.  I am using JSON for all my GET functions.  I can’t even get the syntax to work in Postman.  I will play around with it more next week.  I would also like to use JSON for everything, but as long as I have it working one way or another it doesn’t matter for the application I am writing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Jun 2017 20:10:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541370#M528791</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-06-30T20:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541371#M528792</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have an extra "," (comma) character ending the line:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; "staticProfileAssignment" : false&lt;STRONG&gt;,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Removing it should help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jul 2017 21:19:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541371#M528792</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-07-06T21:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541372#M528793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Awesome that was it!  I was able to do the update with Postman.  Now I will have to change my code to use JSON.  I was able to strip down the JSON to the bare minimum required to update the MAC with a static Identity Group:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To update an existing MAC make a PUT call to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;https://",&lt;/P&gt;&lt;P&gt;    "staticGroupAssignment" : true&lt;/P&gt;&lt;P&gt;  }&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks so much for pointing out that extra comma.  I haven’t worked with JSON much.  I never would have figured that out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paul Haferman&lt;/P&gt;&lt;P&gt;Office- 920.996.3011&lt;/P&gt;&lt;P&gt;Cell- 920.284.9250&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jul 2017 21:43:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541372#M528793</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-07-06T21:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: ERS JSON vs. XML POSTs</title>
      <link>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541373#M528794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am glad that helped. Please note that bulk requests are supported with XML only at the moment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jul 2017 21:52:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ers-json-vs-xml-posts/m-p/3541373#M528794</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-07-06T21:52:58Z</dc:date>
    </item>
  </channel>
</rss>

