<?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 2.4 generate CSR for renew multi-use public certificate in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3696565#M542330</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;Originally, the ISE nodes each had a separate certificate with unique cn e.g. ise-psn.example.com which was used for EAP/admin. The new single certificate with cn=radius.example.com (with all&amp;nbsp;the ISE nodes hostnames as SANs) replaced all the old certificates so it wasn't technically a certificate renewal.&lt;/P&gt;
&lt;P&gt;Cheers&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
    <pubDate>Tue, 28 Aug 2018 21:10:15 GMT</pubDate>
    <dc:creator>andrewswanson</dc:creator>
    <dc:date>2018-08-28T21:10:15Z</dc:date>
    <item>
      <title>ISE 2.4 generate CSR for renew multi-use public certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3692675#M542326</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I tried use ISE to generate CSR for customer renew their public signed certificate, when i choose all nodes of checkbox, it will generate CSR for each node, so when i download it i saw multiple CSR, is it correct?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Subject field&lt;BR /&gt;• CN=ise.abcde.com&lt;BR /&gt;• OU=IT&lt;BR /&gt;• O=ABCDE&lt;BR /&gt;• L=Hong Kong&lt;BR /&gt;• C=HK&lt;/P&gt;
&lt;P&gt;Subject Alternative Name (SAN) field&lt;BR /&gt;• DNS Name: ise.abcde.com&lt;BR /&gt;• DNS Name: ise01.abcde.com&lt;BR /&gt;• DNS Name: ise02.abcde.com&lt;BR /&gt;• DNS Name: ise03.abcde.com&lt;/P&gt;
&lt;P&gt;Signature Algorithm&lt;BR /&gt;• SHA256&lt;/P&gt;
&lt;P&gt;Key Length&lt;BR /&gt;• 2048&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:48:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3692675#M542326</guid>
      <dc:creator>haltong</dc:creator>
      <dc:date>2019-03-11T08:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 generate CSR for renew multi-use public certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3693548#M542327</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I recently done a similar csr for a 5 node 2.3 deployment - when you choose "all nodes" a csr is created for all nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As my csr was for a single certificate for all 5 nodes (cn=radius.example.com with the 5 node's hostnames as SANs) I submitted 1 of these csrs to be signed. When I got the signed certificate back I imported it and bound it to the ISE node&amp;nbsp;the csr came from.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I then exported this certificate/key and imported it onto the other ISE nodes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers&lt;BR /&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 23 Aug 2018 08:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3693548#M542327</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2018-08-23T08:07:50Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 generate CSR for renew multi-use public certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3696374#M542328</link>
      <description>&lt;P&gt;Hi Andy,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for information, seems rest of the CSRs is not necessary from your experience.&lt;/P&gt;
&lt;P&gt;Did you also renew existing public certificate?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 17:24:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3696374#M542328</guid>
      <dc:creator>haltong</dc:creator>
      <dc:date>2018-08-28T17:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 generate CSR for renew multi-use public certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3696565#M542330</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;Originally, the ISE nodes each had a separate certificate with unique cn e.g. ise-psn.example.com which was used for EAP/admin. The new single certificate with cn=radius.example.com (with all&amp;nbsp;the ISE nodes hostnames as SANs) replaced all the old certificates so it wasn't technically a certificate renewal.&lt;/P&gt;
&lt;P&gt;Cheers&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 21:10:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-generate-csr-for-renew-multi-use-public-certificate/m-p/3696565#M542330</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2018-08-28T21:10:15Z</dc:date>
    </item>
  </channel>
</rss>

