<?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 Amitesh, The WLC is the in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726440#M140020</link>
    <description>&lt;P&gt;Hi Amitesh,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The WLC is the authenticator and therefore does not see what type of EAP authentication is used. That is determined by your client and the RADIUS server during what is known as an EAP-Type Request. On the WLC, you need to set the L2 Auth as 802.1x and this is enough to establish the initial communication between the supplicant (wireless client)&amp;nbsp;and the RADIUS server.&lt;/P&gt;&lt;P&gt;If your server is configured for PEAP and your client is too then it should work.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note&lt;/STRONG&gt;: PEAP auth can come in two flavours but by far the most common is PEAP with MSCHAPv2. This requires a certificate to be setup on your RADIUS/NPS server to be used for securing communications. See the following links for help with this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportforums.cisco.com/sites/default/files/legacy/5/5/8/89855-Deploy%20a%20CA%20and%20NPS%20Certificate%20Server.docx"&gt;https://supportforums.cisco.com/sites/default/files/legacy/5/5/8/89855-Deploy%20a%20CA%20and%20NPS%20Certificate%20Server.docx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise#Example_RADIUS_Configuration_(Windows_NPS_.2B_AD)"&gt;https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise#Example_RADIUS_Configuration_(Windows_NPS_.2B_AD)&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Aug 2015 09:43:49 GMT</pubDate>
    <dc:creator>Ric Beeching</dc:creator>
    <dc:date>2015-08-10T09:43:49Z</dc:date>
    <item>
      <title>Client Authentication  Problem</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726439#M140019</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone tell me if i can change the method of authentication to PEAP from EAP on then WLC for a particular SSID. as my end client is having PEAP authentication but my radius is rejecting the Authentication stating that it is not matching with PEAP.&lt;/P&gt;&lt;P&gt;I am not finding the way where i can change the authentication type on WLC to EAP&lt;/P&gt;&lt;P&gt;Thanks in advance !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 10:42:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726439#M140019</guid>
      <dc:creator>amitesh.pandey1</dc:creator>
      <dc:date>2021-07-05T10:42:44Z</dc:date>
    </item>
    <item>
      <title>Hi Amitesh, The WLC is the</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726440#M140020</link>
      <description>&lt;P&gt;Hi Amitesh,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The WLC is the authenticator and therefore does not see what type of EAP authentication is used. That is determined by your client and the RADIUS server during what is known as an EAP-Type Request. On the WLC, you need to set the L2 Auth as 802.1x and this is enough to establish the initial communication between the supplicant (wireless client)&amp;nbsp;and the RADIUS server.&lt;/P&gt;&lt;P&gt;If your server is configured for PEAP and your client is too then it should work.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note&lt;/STRONG&gt;: PEAP auth can come in two flavours but by far the most common is PEAP with MSCHAPv2. This requires a certificate to be setup on your RADIUS/NPS server to be used for securing communications. See the following links for help with this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportforums.cisco.com/sites/default/files/legacy/5/5/8/89855-Deploy%20a%20CA%20and%20NPS%20Certificate%20Server.docx"&gt;https://supportforums.cisco.com/sites/default/files/legacy/5/5/8/89855-Deploy%20a%20CA%20and%20NPS%20Certificate%20Server.docx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise#Example_RADIUS_Configuration_(Windows_NPS_.2B_AD)"&gt;https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_with_WPA2-Enterprise#Example_RADIUS_Configuration_(Windows_NPS_.2B_AD)&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2015 09:43:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726440#M140020</guid>
      <dc:creator>Ric Beeching</dc:creator>
      <dc:date>2015-08-10T09:43:49Z</dc:date>
    </item>
    <item>
      <title>Please check the following</title>
      <link>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726441#M140021</link>
      <description>&lt;P&gt;Please check the following links&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wlan-security/69730-eap-auth-wlc.html&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/100590-ldap-eapfast-config.html&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99791-eapfast-wlc-rad-config.html&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2015 15:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/client-authentication-problem/m-p/2726441#M140021</guid>
      <dc:creator>Prakash Parvathala</dc:creator>
      <dc:date>2015-08-19T15:11:08Z</dc:date>
    </item>
  </channel>
</rss>

