<?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 Unable to Retrieve All Rejected Endpoints Using Cisco ISE API in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/unable-to-retrieve-all-rejected-endpoints-using-cisco-ise-api/m-p/4894738#M583119</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I am wondering if there is any documentation pertaining to the ISE API's handling pagination limits&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When using the Cisco ISE API to fetch all rejected endpoints, I am only receiving a limited set of 100 rejected endpoints, &lt;SPAN&gt;even though there are more rejected endpoints in the Cisco ISE database.&amp;nbsp;&lt;/SPAN&gt;The API should return all rejected endpoints, but it appears to be truncating the results&amp;nbsp;&lt;SPAN&gt;, i&amp;nbsp;can't find any efficient way to retrieve the&lt;/SPAN&gt;&lt;SPAN&gt; endpoints.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i would appreciate any help.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jul 2023 08:22:01 GMT</pubDate>
    <dc:creator>mzarli</dc:creator>
    <dc:date>2023-07-28T08:22:01Z</dc:date>
    <item>
      <title>Unable to Retrieve All Rejected Endpoints Using Cisco ISE API</title>
      <link>https://community.cisco.com/t5/network-access-control/unable-to-retrieve-all-rejected-endpoints-using-cisco-ise-api/m-p/4894738#M583119</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I am wondering if there is any documentation pertaining to the ISE API's handling pagination limits&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;When using the Cisco ISE API to fetch all rejected endpoints, I am only receiving a limited set of 100 rejected endpoints, &lt;SPAN&gt;even though there are more rejected endpoints in the Cisco ISE database.&amp;nbsp;&lt;/SPAN&gt;The API should return all rejected endpoints, but it appears to be truncating the results&amp;nbsp;&lt;SPAN&gt;, i&amp;nbsp;can't find any efficient way to retrieve the&lt;/SPAN&gt;&lt;SPAN&gt; endpoints.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;i would appreciate any help.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2023 08:22:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/unable-to-retrieve-all-rejected-endpoints-using-cisco-ise-api/m-p/4894738#M583119</guid>
      <dc:creator>mzarli</dc:creator>
      <dc:date>2023-07-28T08:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Retrieve All Rejected Endpoints Using Cisco ISE API</title>
      <link>https://community.cisco.com/t5/network-access-control/unable-to-retrieve-all-rejected-endpoints-using-cisco-ise-api/m-p/4895469#M583158</link>
      <description>&lt;P&gt;&lt;A style="box-sizing: inherit; color: var(--cui-link-color); text-decoration: none; appearance: none; border-width: 0px; cursor: pointer; -webkit-font-smoothing: inherit; display: inline-flex; flex-wrap: wrap; font-weight: var(--cui-link-font-weight); background: none; font-family: CiscoSans, Arial, sans-serif; font-size: 20px; font-style: normal; font-variant-caps: normal; letter-spacing: normal; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" href="https://cdetsng.cisco.com/webui/#view=CSCwd18511" target="_blank" rel="noopener"&gt;CSCwd18511&lt;/A&gt; /ers/config/endpoint/getrejectedendpoints NOT RETURNING MORE THAN 100 ENTRIES&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jul 2023 04:03:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/unable-to-retrieve-all-rejected-endpoints-using-cisco-ise-api/m-p/4895469#M583158</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-07-30T04:03:37Z</dc:date>
    </item>
  </channel>
</rss>

