<?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 The only downtime you can in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/renewing-https-certificate-in-cisco-ise/m-p/2986559#M38728</link>
    <description>&lt;P&gt;The only downtime you can expect while renewing the HTTPS certificate is:&lt;/P&gt;
&lt;P&gt;1. For HTTPS protocol changes, a restart of the ISE services is required, which creates a few minutes of downtime. You will not be able to access the GUI for round 10 - 15 minutes.&lt;/P&gt;
&lt;P&gt;2. If you use self-signed certificates in a distributed deployment, the primary self-signed certificate must be installed into the trusted certificate store of the secondary ISE server.&amp;nbsp; Likewise, the secondary self-signed certificate must be installed into the trusted certificate store of the primary ISE server. This allows the ISE servers to mutually authenticate each other.&amp;nbsp; Without this, the deployment might break. If you renew certificates from a third-party CA, verify whether the root certificate chain has changed and update the trusted certificate store in the ISE accordingly.&lt;/P&gt;
&lt;P&gt;Here is &lt;A href="http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116977-technote-ise-cert-00.html"&gt;document&lt;/A&gt; where same steps are documented. I've highlighted for your convenience.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rgds,&lt;/P&gt;
&lt;P&gt;Jatin&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;~ Do rate helpful posts.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 16 Aug 2016 13:27:55 GMT</pubDate>
    <dc:creator>Jatin Katyal</dc:creator>
    <dc:date>2016-08-16T13:27:55Z</dc:date>
    <item>
      <title>Renewing HTTPS Certificate in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/renewing-https-certificate-in-cisco-ise/m-p/2986558#M38727</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;A few months ago a renewed our eap certificate. Now i have to renew the HTTPS certificate. ISE says there will be a "significant" downtime when renewing the certificate.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What is this downtime exactly? Can't users authenticatie through EAP / Radius?&amp;nbsp; Or is it only the web interface? I can't find any documentation on this matter.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Michael Trip&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:59:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/renewing-https-certificate-in-cisco-ise/m-p/2986558#M38727</guid>
      <dc:creator>Michael Trip</dc:creator>
      <dc:date>2019-03-11T06:59:52Z</dc:date>
    </item>
    <item>
      <title>The only downtime you can</title>
      <link>https://community.cisco.com/t5/network-access-control/renewing-https-certificate-in-cisco-ise/m-p/2986559#M38728</link>
      <description>&lt;P&gt;The only downtime you can expect while renewing the HTTPS certificate is:&lt;/P&gt;
&lt;P&gt;1. For HTTPS protocol changes, a restart of the ISE services is required, which creates a few minutes of downtime. You will not be able to access the GUI for round 10 - 15 minutes.&lt;/P&gt;
&lt;P&gt;2. If you use self-signed certificates in a distributed deployment, the primary self-signed certificate must be installed into the trusted certificate store of the secondary ISE server.&amp;nbsp; Likewise, the secondary self-signed certificate must be installed into the trusted certificate store of the primary ISE server. This allows the ISE servers to mutually authenticate each other.&amp;nbsp; Without this, the deployment might break. If you renew certificates from a third-party CA, verify whether the root certificate chain has changed and update the trusted certificate store in the ISE accordingly.&lt;/P&gt;
&lt;P&gt;Here is &lt;A href="http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116977-technote-ise-cert-00.html"&gt;document&lt;/A&gt; where same steps are documented. I've highlighted for your convenience.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Rgds,&lt;/P&gt;
&lt;P&gt;Jatin&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;~ Do rate helpful posts.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2016 13:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/renewing-https-certificate-in-cisco-ise/m-p/2986559#M38728</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2016-08-16T13:27:55Z</dc:date>
    </item>
  </channel>
</rss>

