<?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: ISE 1.2 CRL in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300950#M107423</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE&amp;nbsp;&amp;nbsp;&amp;nbsp; supports two ways of checking the revocation status of a client&amp;nbsp; or&amp;nbsp; server&amp;nbsp;&amp;nbsp; certificate that is issued by a particular CA. The first is&amp;nbsp; to&amp;nbsp; validate the&amp;nbsp;&amp;nbsp; certificate using the Online Certificate Status&amp;nbsp; Protocol&amp;nbsp; (OCSP), which makes&amp;nbsp;&amp;nbsp; a request to an OCSP service maintained&amp;nbsp; by the CA.&amp;nbsp; The second is to validate&amp;nbsp;&amp;nbsp; the certificate against a&amp;nbsp; Certificate&amp;nbsp; Revocation List (CRL) which is&amp;nbsp;&amp;nbsp; downloaded from the CA&amp;nbsp; into ISE. Both&amp;nbsp; of these methods can be enabled, in&amp;nbsp;&amp;nbsp; which case OCSP is&amp;nbsp; used first, and&amp;nbsp; only if a status determination cannot be&amp;nbsp;&amp;nbsp; made then&amp;nbsp; the CRL is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Please check the below links&amp;nbsp; which can be helpful in configurations:&lt;/STRONG&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link-1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_man_cert.html" rel="nofollow"&gt;http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_man_cert.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Sep 2013 16:26:42 GMT</pubDate>
    <dc:creator>aqjaved</dc:creator>
    <dc:date>2013-09-23T16:26:42Z</dc:date>
    <item>
      <title>ISE 1.2 CRL</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300949#M107386</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Quick one this time...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What box is requesting the CRL? the ADM or the PSN?&lt;/P&gt;&lt;P&gt;am right to assum that the port 80 need to be open on the FW&amp;nbsp; from ADM or PSN&amp;nbsp; to the CRL location&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:53:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300949#M107386</guid>
      <dc:creator>eric.lessard</dc:creator>
      <dc:date>2019-03-11T03:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 1.2 CRL</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300950#M107423</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE&amp;nbsp;&amp;nbsp;&amp;nbsp; supports two ways of checking the revocation status of a client&amp;nbsp; or&amp;nbsp; server&amp;nbsp;&amp;nbsp; certificate that is issued by a particular CA. The first is&amp;nbsp; to&amp;nbsp; validate the&amp;nbsp;&amp;nbsp; certificate using the Online Certificate Status&amp;nbsp; Protocol&amp;nbsp; (OCSP), which makes&amp;nbsp;&amp;nbsp; a request to an OCSP service maintained&amp;nbsp; by the CA.&amp;nbsp; The second is to validate&amp;nbsp;&amp;nbsp; the certificate against a&amp;nbsp; Certificate&amp;nbsp; Revocation List (CRL) which is&amp;nbsp;&amp;nbsp; downloaded from the CA&amp;nbsp; into ISE. Both&amp;nbsp; of these methods can be enabled, in&amp;nbsp;&amp;nbsp; which case OCSP is&amp;nbsp; used first, and&amp;nbsp; only if a status determination cannot be&amp;nbsp;&amp;nbsp; made then&amp;nbsp; the CRL is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;STRONG&gt;Please check the below links&amp;nbsp; which can be helpful in configurations:&lt;/STRONG&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Link-1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_man_cert.html" rel="nofollow"&gt;http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_man_cert.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Sep 2013 16:26:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300950#M107423</guid>
      <dc:creator>aqjaved</dc:creator>
      <dc:date>2013-09-23T16:26:42Z</dc:date>
    </item>
    <item>
      <title>ISE 1.2 CRL</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300951#M107473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thx Ageel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After testing, all the box need to be able to acess the CRL, not only the PSN&lt;/P&gt;&lt;P&gt;second fact is that the HTTPS protocol needs to be binded to the CA root Cert in order to Download the CRL.&lt;/P&gt;&lt;P&gt;If your https is binded to a self sign, the Admin node wont be able to DL it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Sep 2013 16:31:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-2-crl/m-p/2300951#M107473</guid>
      <dc:creator>eric.lessard</dc:creator>
      <dc:date>2013-09-23T16:31:55Z</dc:date>
    </item>
  </channel>
</rss>

