<?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: Cisco ISE 2.3 - Certificate use in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705480#M493421</link>
    <description>&lt;P&gt;Did you double check the cert you got back from the provider to ensure the CN field or SAN field has the FQDN of the primary node?&amp;nbsp; You can do everything with one cert if you want.&amp;nbsp; Just use SAN fields to cover both nodes.&amp;nbsp; It makes things easier at the time of renewal and having a single EAP certificate makes mobile devices have less issues if they have to switch to the other PSN to authenticate.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Sep 2018 12:15:15 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2018-09-12T12:15:15Z</dc:date>
    <item>
      <title>Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705462#M493420</link>
      <description>&lt;P&gt;Hello Everyone ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a 2 PAN &amp;amp; PSN nodes deployment , the one acts as Primary (Admin and monitoring) and other one as Secondary&amp;nbsp;&lt;SPAN&gt;(Admin and monitoring) .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We had to replace the Admin,Portal and EAP Cerificate with new ones due to expiration .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;So we created 2 CSRs and we get the Certificates from our provider .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Then we successfully bind the 2 Certificates with CSRs but initially we did not gave any use to Certificates .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;After Successfully binding we proceed with giving the certificates the usage we wanted (Admin,EAP ,Portal) .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We first begin from Secondary Node with success the managed .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;When we tried to do it on Primary we get the following error .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;"Certificate must contain the FQDN '' or a matching wildcard as a DNS name in the SubjectAlternativeName (SAN) extension."&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The CSRs had no difference in production and the certificatesd we get back also .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is anyone has any similar problem or has any idea what is going on ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2018 11:41:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705462#M493420</guid>
      <dc:creator>pgiouvanellis</dc:creator>
      <dc:date>2018-09-12T11:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705480#M493421</link>
      <description>&lt;P&gt;Did you double check the cert you got back from the provider to ensure the CN field or SAN field has the FQDN of the primary node?&amp;nbsp; You can do everything with one cert if you want.&amp;nbsp; Just use SAN fields to cover both nodes.&amp;nbsp; It makes things easier at the time of renewal and having a single EAP certificate makes mobile devices have less issues if they have to switch to the other PSN to authenticate.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2018 12:15:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705480#M493421</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-09-12T12:15:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705488#M493422</link>
      <description>Great section in admin guide&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_0111.html#ID71" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_0111.html#ID71&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 12 Sep 2018 12:19:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705488#M493422</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-09-12T12:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705512#M493424</link>
      <description>&lt;P&gt;I double check everything ,&lt;/P&gt;
&lt;P&gt;The odd is that the other certificate which is exactly the same just with different FQDN and SAN was imported successfully with no errors .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How it is possible to add SAN field to Cert right know ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You mean that i have to generate new CSR with SAN Field import 2 FQDNs one for each node ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank You&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2018 12:34:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705512#M493424</guid>
      <dc:creator>pgiouvanellis</dc:creator>
      <dc:date>2018-09-12T12:34:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705702#M493425</link>
      <description>Yes, generate a new CSR with SAN fields to cover every FQDN.  Then you have one cert/private key to manage.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 12 Sep 2018 16:10:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3705702#M493425</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-09-12T16:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE 2.3 - Certificate use</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3706242#M493427</link>
      <description>&lt;P&gt;Hello ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;FYI&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yesterday we have import the new certificate for EAP and Portals and we left the Admin Portal ,&lt;/P&gt;
&lt;P&gt;since it does not mind us .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After a little time the Portal did not worked properly they were not accessible from anywhere .&lt;/P&gt;
&lt;P&gt;The EAP authentication was working properly .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After application stop and application start the problem was solved we were able to&amp;nbsp;&lt;/P&gt;
&lt;P&gt;assign the certificate to Admin Portal and Portals was working properly .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a walk through that we performed and we manage to bring ISE in working state .&lt;/P&gt;</description>
      <pubDate>Thu, 13 Sep 2018 12:41:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-2-3-certificate-use/m-p/3706242#M493427</guid>
      <dc:creator>pgiouvanellis</dc:creator>
      <dc:date>2018-09-13T12:41:44Z</dc:date>
    </item>
  </channel>
</rss>

