<?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 HI Attila, in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819491#M56732</link>
    <description>&lt;P&gt;HI Attila,&lt;/P&gt;
&lt;P&gt;It seems your question is specifically for client / user certificate. &lt;A href="https://technet.microsoft.com/en-us/library/cc731363%28v=ws.10%29.aspx"&gt;Certificate Requirement with PEAP &amp;amp; EAP&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you're planning to use wild card certificate. Please ensure you follow this document to get the right certificates. &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_man_cert.html#pgfId-1171325"&gt;Wild Card with ISE&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The Enhanced Key Usage field identifies the intended purpose of the certificate and needs to contain Client Authentication. This field is mandatory when you use the Microsoft supplicant for PEAP and EAP-TLS.&lt;/P&gt;
&lt;P&gt;If you request a certificate with the use of a CSR with Microsoft Certificate Services, you do not have the option to specify the Intended Purpose with the Standalone CA. Therefore, the EKU field is absent. With the Enterprise CA, you have the Intended Purpose drop-down. Some CAs do not create certificates with an EKU field. They are useless when you use the Microsoft EAP supplicant.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jatin&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 15 Nov 2015 08:35:25 GMT</pubDate>
    <dc:creator>Jatin Katyal</dc:creator>
    <dc:date>2015-11-15T08:35:25Z</dc:date>
    <item>
      <title>ISE certificate requirements for EAP-TLS</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819489#M56728</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to connect our corporate tablets and mobile devices to a restricted network - without implementing classic BYOD features like&amp;nbsp;&lt;/P&gt;
&lt;P&gt;self-provisioning but with certificate based only authentication (EAP-TLS).&lt;/P&gt;
&lt;P&gt;(Our Helpdesk will handle the certificate install, wireless network set, etc.)&lt;/P&gt;
&lt;P&gt;The WLC side is configured to handle the TLS, and now we try to generate certificates. To Ipad, to Android (Galaxy Tab 3 KITKAT), and to iphone.&lt;/P&gt;
&lt;P&gt;Is there any special certificate requirements to implement this?&lt;/P&gt;
&lt;P&gt;What should certificate EKU field contain?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819489#M56728</guid>
      <dc:creator>Attila Horvath</dc:creator>
      <dc:date>2019-03-11T06:13:48Z</dc:date>
    </item>
    <item>
      <title>I think this doc may be</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819490#M56731</link>
      <description>&lt;P&gt;I think&amp;nbsp;this doc may be useful:&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine-software/116068-configure-product-00.html&lt;/P&gt;
&lt;P&gt;It has some details on the EKU field and certificate template.&lt;/P&gt;
&lt;P&gt;Other consideration: if you are planning to issue wildcard certificate to the clients, make sure the subject doesn't contain the wildcard or windows clients will have problem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2015 23:13:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819490#M56731</guid>
      <dc:creator>kurmai</dc:creator>
      <dc:date>2015-11-12T23:13:23Z</dc:date>
    </item>
    <item>
      <title>HI Attila,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819491#M56732</link>
      <description>&lt;P&gt;HI Attila,&lt;/P&gt;
&lt;P&gt;It seems your question is specifically for client / user certificate. &lt;A href="https://technet.microsoft.com/en-us/library/cc731363%28v=ws.10%29.aspx"&gt;Certificate Requirement with PEAP &amp;amp; EAP&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If you're planning to use wild card certificate. Please ensure you follow this document to get the right certificates. &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/user_guide/ise_user_guide/ise_man_cert.html#pgfId-1171325"&gt;Wild Card with ISE&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The Enhanced Key Usage field identifies the intended purpose of the certificate and needs to contain Client Authentication. This field is mandatory when you use the Microsoft supplicant for PEAP and EAP-TLS.&lt;/P&gt;
&lt;P&gt;If you request a certificate with the use of a CSR with Microsoft Certificate Services, you do not have the option to specify the Intended Purpose with the Standalone CA. Therefore, the EKU field is absent. With the Enterprise CA, you have the Intended Purpose drop-down. Some CAs do not create certificates with an EKU field. They are useless when you use the Microsoft EAP supplicant.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jatin&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 15 Nov 2015 08:35:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-certificate-requirements-for-eap-tls/m-p/2819491#M56732</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2015-11-15T08:35:25Z</dc:date>
    </item>
  </channel>
</rss>

