<?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: Combining or chaining root and intermediate certs in ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/combining-or-chaining-root-and-intermediate-certs-in-ise/m-p/3509283#M517530</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For ISE, we usually import first the root CA certificate into the Trusted Certificates store, followed by any intermediate CA certificates into the same store, and finally import the portal certificate as a system certificate and designate it with a portal tag. This way ISE should be able to build and send the full chain to the endpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If root or intermediate CA certificates imported after the system certificate, then ISE services need a restart for it to send the full chain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it does not work as the above, please engage TAC to troubleshoot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Feb 2018 16:31:58 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2018-02-28T16:31:58Z</dc:date>
    <item>
      <title>Combining or chaining root and intermediate certs in ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/combining-or-chaining-root-and-intermediate-certs-in-ise/m-p/3509282#M517528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a customer having issues with endpoints that do not have the intermediate or root certs downloaded previously on their system. This prevents their access because they can not make the chain to the root to say that the domain's guest portal cert is valid. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some other NAC solutions allow the chaining of multiple certificate public keys in the same file, not sure if that is doable in ISE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Feb 2018 14:14:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/combining-or-chaining-root-and-intermediate-certs-in-ise/m-p/3509282#M517528</guid>
      <dc:creator>mmcphee</dc:creator>
      <dc:date>2018-02-28T14:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: Combining or chaining root and intermediate certs in ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/combining-or-chaining-root-and-intermediate-certs-in-ise/m-p/3509283#M517530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For ISE, we usually import first the root CA certificate into the Trusted Certificates store, followed by any intermediate CA certificates into the same store, and finally import the portal certificate as a system certificate and designate it with a portal tag. This way ISE should be able to build and send the full chain to the endpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If root or intermediate CA certificates imported after the system certificate, then ISE services need a restart for it to send the full chain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it does not work as the above, please engage TAC to troubleshoot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Feb 2018 16:31:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/combining-or-chaining-root-and-intermediate-certs-in-ise/m-p/3509283#M517530</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-02-28T16:31:58Z</dc:date>
    </item>
  </channel>
</rss>

