<?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 ISE API with UTF-8 character in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-api-with-utf-8-character/m-p/3526694#M508697</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our customer is doing test about API, they found the response from API did not show OU information as expected, but they could see OU information in live session log. My guess is it's relative with UTF-8. If you have same experience or any suggestion will be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;API output:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WechatIMG20.jpeg" class="jive-image image-3" src="https://community.cisco.com/legacyfs/online/fusion/118550_WechatIMG20.jpeg" style="height: 303px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;ISE live log:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WechatIMG19.jpeg" class="jive-image image-2" src="https://community.cisco.com/legacyfs/online/fusion/118540_WechatIMG19.jpeg" style="caret-color: #000000; color: #000000; font-family: -webkit-standard; height: 271px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;DL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jul 2018 08:41:17 GMT</pubDate>
    <dc:creator>yongwli</dc:creator>
    <dc:date>2018-07-10T08:41:17Z</dc:date>
    <item>
      <title>ISE API with UTF-8 character</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-with-utf-8-character/m-p/3526694#M508697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our customer is doing test about API, they found the response from API did not show OU information as expected, but they could see OU information in live session log. My guess is it's relative with UTF-8. If you have same experience or any suggestion will be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;API output:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WechatIMG20.jpeg" class="jive-image image-3" src="https://community.cisco.com/legacyfs/online/fusion/118550_WechatIMG20.jpeg" style="height: 303px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;ISE live log:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WechatIMG19.jpeg" class="jive-image image-2" src="https://community.cisco.com/legacyfs/online/fusion/118540_WechatIMG19.jpeg" style="caret-color: #000000; color: #000000; font-family: -webkit-standard; height: 271px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;DL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2018 08:41:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-with-utf-8-character/m-p/3526694#M508697</guid>
      <dc:creator>yongwli</dc:creator>
      <dc:date>2018-07-10T08:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE API with UTF-8 character</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-api-with-utf-8-character/m-p/3526695#M508698</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's best to engage TAC and ask TAC to recreate and log a bug.&lt;/P&gt;&lt;P&gt;If that is not possible, I need more info on which particular ISE API is used. It's hard to tell from the output but I am guessing it M&amp;amp;T session API.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2018 19:49:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-api-with-utf-8-character/m-p/3526695#M508698</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-07-10T19:49:46Z</dc:date>
    </item>
  </channel>
</rss>

