<?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: WPA2 Enterprise EAP-TLS authentication in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173272#M1075139</link>
    <description>&lt;P&gt;Thank you for reaching out.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I connect an MCU to ISE? In the official documentation, there were only windows, macOS, android, and ios. but how do I connect an embedded device?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 25 Oct 2020 17:47:41 GMT</pubDate>
    <dc:creator>170232D14065</dc:creator>
    <dc:date>2020-10-25T17:47:41Z</dc:date>
    <item>
      <title>WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173237#M1075133</link>
      <description>&lt;P&gt;I need to connect my IoT embedded devices to a CISCO-ISE managed enterprise wireless network using WPA2E and EAP-TLS protocol for authentication. When I go through the cisco compatibility documentation for client devices there was nothing about the embedded devices. So my question is, what are the compatibility concerns when it comes to connecting an embedded device which simply consists of an MCU and some peripherals through certificate-based authentication? There were documents only regarding connection of mainstream devices like Pc, laptop, smartphone but none about MCU.&lt;/P&gt;&lt;P&gt;thank you&lt;/P&gt;</description>
      <pubDate>Sun, 25 Oct 2020 17:43:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173237#M1075133</guid>
      <dc:creator>170232D14065</dc:creator>
      <dc:date>2020-10-25T17:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173240#M1075134</link>
      <description>&lt;P&gt;If the IoT device uses standard RADIUS protocol attributes then I think you can just add it as a normal network device to ISE, that should work. However, if it uses customized RADIUS attributes, then you need to create a network device profile with those customized attributes, and then when you add it as a network device, you need to associate the profile you created to that device from the Device Profile menu.&lt;/P&gt;</description>
      <pubDate>Sun, 25 Oct 2020 16:05:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173240#M1075134</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2020-10-25T16:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173272#M1075139</link>
      <description>&lt;P&gt;Thank you for reaching out.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I connect an MCU to ISE? In the official documentation, there were only windows, macOS, android, and ios. but how do I connect an embedded device?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Oct 2020 17:47:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173272#M1075139</guid>
      <dc:creator>170232D14065</dc:creator>
      <dc:date>2020-10-25T17:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173282#M1075145</link>
      <description>&lt;P&gt;Is the MCU connected to the network and can reach ISE through the network?&lt;/P&gt;</description>
      <pubDate>Sun, 25 Oct 2020 18:09:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173282#M1075145</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2020-10-25T18:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173382#M1075170</link>
      <description>&lt;P&gt;it's in the wifi authentication phase. I think the ISE acts as the radius server for the access point. so it's about authenticating the device (wifi chip) to the network.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2020 03:25:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173382#M1075170</guid>
      <dc:creator>170232D14065</dc:creator>
      <dc:date>2020-10-26T03:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173389#M1075172</link>
      <description>&lt;P&gt;If the MCU connects to the access point, then the access point should be added to ISE as a network device, since the access point will be the RADIUS authenticator and the MCU will be the supplicant. The SSID on the access point should be configured for dot1x as well.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2020 03:52:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173389#M1075172</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2020-10-26T03:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173406#M1075175</link>
      <description>&lt;P&gt;So it seems it is all good if the device supports standard RADIUS protocol attributes.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you direct me to some resources describing the implementation of EAP-TLS on a microcontroller?&lt;/P&gt;&lt;P&gt;So far I didn't find any guidance docs. The only thing having is a secure connection to a web server through certificate-based authentication, but nothing about WiFi authentication using ca.&lt;/P&gt;&lt;P&gt;Thank you so much for clarifying things.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2020 05:05:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173406#M1075175</guid>
      <dc:creator>170232D14065</dc:creator>
      <dc:date>2020-10-26T05:05:25Z</dc:date>
    </item>
    <item>
      <title>Re: WPA2 Enterprise EAP-TLS authentication</title>
      <link>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173893#M1075215</link>
      <description>&lt;P&gt;I am really sorry, but did not come across those MCU in practice.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Oct 2020 18:28:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/wpa2-enterprise-eap-tls-authentication/m-p/4173893#M1075215</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2020-10-26T18:28:01Z</dc:date>
    </item>
  </channel>
</rss>

