<?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 Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361191#M599539</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to renew a certificate that is expiring soon, which is used for Admin access, EAP authentication, and RADIUS DTLS.&lt;BR /&gt;This certificate is signed by our internal certification authority.&lt;/P&gt;&lt;P&gt;I generate a CSR and sign it with our certification authority, but when I attempt to bind the certificate using the Bind button, the following error is displayed:&amp;nbsp;&lt;SPAN&gt;Certificate path validation failed. Make sure required Certificate Chain is imported under Trusted Certificates.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Of course, both our subordinate CA and root CA are uploaded in the Trusted Certificates store.We are running version 2.6.0.156.&lt;BR /&gt;Am I missing something?&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jan 2026 13:38:42 GMT</pubDate>
    <dc:creator>CARGO</dc:creator>
    <dc:date>2026-01-14T13:38:42Z</dc:date>
    <item>
      <title>Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361191#M599539</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to renew a certificate that is expiring soon, which is used for Admin access, EAP authentication, and RADIUS DTLS.&lt;BR /&gt;This certificate is signed by our internal certification authority.&lt;/P&gt;&lt;P&gt;I generate a CSR and sign it with our certification authority, but when I attempt to bind the certificate using the Bind button, the following error is displayed:&amp;nbsp;&lt;SPAN&gt;Certificate path validation failed. Make sure required Certificate Chain is imported under Trusted Certificates.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Of course, both our subordinate CA and root CA are uploaded in the Trusted Certificates store.We are running version 2.6.0.156.&lt;BR /&gt;Am I missing something?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 13:38:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361191#M599539</guid>
      <dc:creator>CARGO</dc:creator>
      <dc:date>2026-01-14T13:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361204#M599543</link>
      <description>&lt;P&gt;Without seeing certs not exactly sure, but at our org they recently updated the sub cert, so make sure if they have updated the sub or rootCA cert you import those.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 14:04:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361204#M599543</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2026-01-14T14:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361235#M599544</link>
      <description>&lt;P&gt;Yes, you are right — the issuing CA was updated and I wasn’t aware of it.&lt;BR /&gt;Thank you very much.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 16:18:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361235#M599544</guid>
      <dc:creator>CARGO</dc:creator>
      <dc:date>2026-01-14T16:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361269#M599545</link>
      <description>&lt;P&gt;Glad it worked, now the other fun is do devices have the new cert. We ran into devices not trusting ISE for auth since it was now signed with the new cert authority it didn't trust. Just something to watch for if devices stop 802.1x.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jan 2026 17:08:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise/m-p/5361269#M599545</guid>
      <dc:creator>Dustin Anderson</dc:creator>
      <dc:date>2026-01-14T17:08:14Z</dc:date>
    </item>
  </channel>
</rss>

