<?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: Certs in Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5088124#M589226</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1149933"&gt;@Gioacchino&lt;/a&gt;&amp;nbsp;- there is a &lt;A href="https://community.cisco.com/t5/network-access-control/ise-certificate-stale-status/td-p/4653889" target="_self"&gt;previous posting about this that explains&lt;/A&gt; why Cisco did this. It's apparently helping us to find certs that are still valid (in terms of date range) but not effectively aligned to an ISE node. I personally don't like this feature because I have found it to be wrong in cases of Guest Portals. ISE gets confused when the PSN node name does not match the cert's CN (two things that have nothing to do with each other and don't need to be identical).&lt;/P&gt;</description>
    <pubDate>Thu, 02 May 2024 20:41:25 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2024-05-02T20:41:25Z</dc:date>
    <item>
      <title>Certs in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5087416#M589207</link>
      <description>&lt;P&gt;Excellent article &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/25619"&gt;@thomas&lt;/a&gt; (weird I cannot tag him),&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/how-to-implement-digital-certificates-in-ise/ta-p/3630897#toc-hId--379707072" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/security-knowledge-base/how-to-implement-digital-certificates-in-ise/ta-p/3630897#toc-hId--379707072&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I wonder if the STALE topic has been taken into account (I don't seem to see it), especially when it comes to EAP certificates, where are explicitly told that their CNs might have nothing to do with the ISE nodes names (and this may definitely trigger the STALE flag)&lt;/P&gt;&lt;P&gt;Gio&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 09:32:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5087416#M589207</guid>
      <dc:creator>Gioacchino</dc:creator>
      <dc:date>2024-05-03T09:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: Certs in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5088124#M589226</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1149933"&gt;@Gioacchino&lt;/a&gt;&amp;nbsp;- there is a &lt;A href="https://community.cisco.com/t5/network-access-control/ise-certificate-stale-status/td-p/4653889" target="_self"&gt;previous posting about this that explains&lt;/A&gt; why Cisco did this. It's apparently helping us to find certs that are still valid (in terms of date range) but not effectively aligned to an ISE node. I personally don't like this feature because I have found it to be wrong in cases of Guest Portals. ISE gets confused when the PSN node name does not match the cert's CN (two things that have nothing to do with each other and don't need to be identical).&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 20:41:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5088124#M589226</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-05-02T20:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Certs in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5088525#M589232</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;I have just wondered if this algorithm would apply to EAP auth certs as well, where indeed the CN of the returned cert might have nothing to do with the ISE nodes and the names given it.&lt;/P&gt;&lt;P&gt;My understanding is that Cisco devs didn't do any distinction.&lt;/P&gt;&lt;P&gt;Regards, Gio&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 09:31:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5088525#M589232</guid>
      <dc:creator>Gioacchino</dc:creator>
      <dc:date>2024-05-03T09:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: Certs in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5094850#M589330</link>
      <description>&lt;P&gt;Unfortunately I don't know how this mechanism works or why we need it.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 00:18:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certs-in-cisco-ise/m-p/5094850#M589330</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-05-09T00:18:29Z</dc:date>
    </item>
  </channel>
</rss>

