<?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.7 EAP Certificate in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4149071#M562767</link>
    <description>&lt;P&gt;Thank you for the reply.&amp;nbsp; The CN would be ise.xyz.local and the wildcard in the SAN would be *.xyz.com.&amp;nbsp; Will this work?&lt;/P&gt;</description>
    <pubDate>Thu, 10 Sep 2020 11:34:56 GMT</pubDate>
    <dc:creator>jrmildren</dc:creator>
    <dc:date>2020-09-10T11:34:56Z</dc:date>
    <item>
      <title>ISE 2.7 EAP Certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4148805#M562756</link>
      <description>&lt;P&gt;I am deploying ISE 2.7. For the EAP certificate is it possible to use a publicly signed certificate then import the same certificate into all of the PSNs? This would simplify things and eliminate devices that are not part of the domain from seeing an untrusted certificate warning.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2020 01:56:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4148805#M562756</guid>
      <dc:creator>jrmildren</dc:creator>
      <dc:date>2020-09-10T01:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 EAP Certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4148824#M562759</link>
      <description>&lt;P&gt;That is actually the recommended approach but the certificate has to be a wildcard certificate.&amp;nbsp; Ensure the Subject/Common Name (CN) is set to one of the ISE nodes' FQDN and then use the wildcard as a SAN DNS Name such as *.mycompany.com.&amp;nbsp; The Subject/CN cannot be a wildcard or Windows clients will complain.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2020 03:16:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4148824#M562759</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-09-10T03:16:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 EAP Certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4149071#M562767</link>
      <description>&lt;P&gt;Thank you for the reply.&amp;nbsp; The CN would be ise.xyz.local and the wildcard in the SAN would be *.xyz.com.&amp;nbsp; Will this work?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2020 11:34:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4149071#M562767</guid>
      <dc:creator>jrmildren</dc:creator>
      <dc:date>2020-09-10T11:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 EAP Certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4149153#M562770</link>
      <description>&lt;P&gt;That is correct!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2020 13:55:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-eap-certificate/m-p/4149153#M562770</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2020-09-10T13:55:53Z</dc:date>
    </item>
  </channel>
</rss>

