<?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 Local Auth issues with Android devices in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466974#M291284</link>
    <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;I am trying to get Meraki local authentication working for Wi-Fi device with eap-tls authentication.&lt;/P&gt;&lt;P&gt;Current topology:&lt;/P&gt;&lt;P&gt;- Azure AD joined windows and android devices (dedicated).&lt;/P&gt;&lt;P&gt;- SCEP certs deployed to clients.&lt;/P&gt;&lt;P&gt;- Root cert uploaded to meraki wifi ssid with local auth enabled.&lt;/P&gt;&lt;P&gt;- OCSP configured and test.&lt;/P&gt;&lt;P&gt;- Wi-Fi profile getting deployed via Intune.&lt;/P&gt;&lt;P&gt;What works:&lt;/P&gt;&lt;P&gt;- Windows clients can successfully connect to Wi-Fi with EAP-TLS when using this setup and OCSP checks work as well.&lt;/P&gt;&lt;P&gt;What does not work:&lt;/P&gt;&lt;P&gt;- Android devices fail the authentication when using "anonmyous" as outer identity (identity privacy).&lt;/P&gt;&lt;P&gt;What I have tried.&lt;/P&gt;&lt;P&gt;- Turning off OCSP verification - Does not help.&lt;/P&gt;&lt;P&gt;-  Start a packet capture with wireshark - I can see that the client send the correct certificate to Meraki however gets a EAP failure code - trying to figure out why.&lt;/P&gt;&lt;P&gt;Workaround I found:&lt;/P&gt;&lt;P&gt;- When deploying the Wi-Fi configuration changing the outer identity field to the common name of the device certificate makes this authentication work.&lt;/P&gt;&lt;P&gt;However, this is not ideal as you will need to deploy a separate profile to each device with their own cert Common name as outer identity which would be a management nightmare.&lt;/P&gt;&lt;P&gt;Also, based on my experience the outer identity text should not matter as it is just used to create a secure tunnel to send inner identity credentials.&lt;/P&gt;&lt;P&gt;I am looking for some help to resolve this issue.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jun 2023 14:09:11 GMT</pubDate>
    <dc:creator>PPatel3</dc:creator>
    <dc:date>2023-06-05T14:09:11Z</dc:date>
    <item>
      <title>Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466974#M291284</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;I am trying to get Meraki local authentication working for Wi-Fi device with eap-tls authentication.&lt;/P&gt;&lt;P&gt;Current topology:&lt;/P&gt;&lt;P&gt;- Azure AD joined windows and android devices (dedicated).&lt;/P&gt;&lt;P&gt;- SCEP certs deployed to clients.&lt;/P&gt;&lt;P&gt;- Root cert uploaded to meraki wifi ssid with local auth enabled.&lt;/P&gt;&lt;P&gt;- OCSP configured and test.&lt;/P&gt;&lt;P&gt;- Wi-Fi profile getting deployed via Intune.&lt;/P&gt;&lt;P&gt;What works:&lt;/P&gt;&lt;P&gt;- Windows clients can successfully connect to Wi-Fi with EAP-TLS when using this setup and OCSP checks work as well.&lt;/P&gt;&lt;P&gt;What does not work:&lt;/P&gt;&lt;P&gt;- Android devices fail the authentication when using "anonmyous" as outer identity (identity privacy).&lt;/P&gt;&lt;P&gt;What I have tried.&lt;/P&gt;&lt;P&gt;- Turning off OCSP verification - Does not help.&lt;/P&gt;&lt;P&gt;-  Start a packet capture with wireshark - I can see that the client send the correct certificate to Meraki however gets a EAP failure code - trying to figure out why.&lt;/P&gt;&lt;P&gt;Workaround I found:&lt;/P&gt;&lt;P&gt;- When deploying the Wi-Fi configuration changing the outer identity field to the common name of the device certificate makes this authentication work.&lt;/P&gt;&lt;P&gt;However, this is not ideal as you will need to deploy a separate profile to each device with their own cert Common name as outer identity which would be a management nightmare.&lt;/P&gt;&lt;P&gt;Also, based on my experience the outer identity text should not matter as it is just used to create a secure tunnel to send inner identity credentials.&lt;/P&gt;&lt;P&gt;I am looking for some help to resolve this issue.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 14:09:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466974#M291284</guid>
      <dc:creator>PPatel3</dc:creator>
      <dc:date>2023-06-05T14:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466975#M291285</link>
      <description>&lt;P&gt;EAP-TLS with which protocol WPA2 or WPA3?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 15:26:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466975#M291285</guid>
      <dc:creator>DainBrammage</dc:creator>
      <dc:date>2023-06-05T15:26:15Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466976#M291286</link>
      <description>&lt;P&gt;WAP2&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 17:19:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466976#M291286</guid>
      <dc:creator>PPatel3</dc:creator>
      <dc:date>2023-06-05T17:19:15Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466977#M291287</link>
      <description>&lt;P&gt;Are you using an alternate management interface for RADIUS?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 20:19:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466977#M291287</guid>
      <dc:creator>DainBrammage</dc:creator>
      <dc:date>2023-06-05T20:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466978#M291288</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Sorry for the delayed reply. We are not using the alternate management interface.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 13:43:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466978#M291288</guid>
      <dc:creator>PPatel3</dc:creator>
      <dc:date>2023-06-07T13:43:02Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466979#M291289</link>
      <description>&lt;P&gt;Found the solution for this issue after working with Meraki support.&lt;/P&gt;&lt;P&gt;Apparently, either the Common Name or Subject Alternative Name of the SCEP cert deployed to android devices must match the outer identity configured in the Wi-Fi profile for Meraki AP to accept it. Issuing a new certificate with a different SAN and using this value as the outer identity in the Wi-Fi profile deployed by Intune, resolved the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2023 12:46:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466979#M291289</guid>
      <dc:creator>PPatel3</dc:creator>
      <dc:date>2023-06-20T12:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466980#M291290</link>
      <description>&lt;P&gt;Hi - We are also trying to get this to work (exact the same topology)  but not able to get this working with certificate on a WIN10 client. User auth is working well (local auth with  SLDAP AAD). Meraki AP is showing a problem with the internal Radius of the MR:&lt;/P&gt;&lt;P&gt;Client failed 802.1X authentication to the RADIUS server.&lt;SPAN class=""&gt; auth_mode='wpa2-802.1x' radius_proto='ipv4' radius_ip='127.0.0.1' reason='radius_login_failure' radio='1' vap='0' channel='44' rssi='47'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Client made an 802.1X authentication request to the RADIUS server, but it did not respond. auth_mode='wpa2-802.1x' radius_proto='ipv4' radius_ip='127.0.0.1' details='conn_refused' reason='radius_timeout' radio='1' vap='0' channel='44' rssi='48'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;At this point meraki support is looking in to this problem but for now no sollution yet. We have tested with a MR33 and &lt;SPAN class=""&gt;CW9166I&lt;/SPAN&gt; accespoint. MB we are doing some wrong configuration (followed this reference &lt;A href="https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X" target="_blank" rel="noopener nofollow noreferrer"&gt;https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X&lt;/A&gt;)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Is it possible that you can share some configuration to check if we have the correct setup.&lt;/P&gt;&lt;P&gt;Thanks in advance - PietK&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2023 15:27:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466980#M291290</guid>
      <dc:creator>theob</dc:creator>
      <dc:date>2023-09-14T15:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: Local Auth issues with Android devices</title>
      <link>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466981#M291291</link>
      <description>&lt;P&gt;Hi, we just resolved this issue. &lt;BR /&gt;Solution : Install the IdenTrust Root CA 1 certificate on your end devices.&lt;BR /&gt;Please refer to : : &lt;A href="https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Auth. configuration-2.JPG" style="width: 828px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.jpeg"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/271506i8BA6EEDF7AF07246/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.jpeg" alt="image.jpeg" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 13:22:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/local-auth-issues-with-android-devices/m-p/5466981#M291291</guid>
      <dc:creator>bdcvc</dc:creator>
      <dc:date>2023-09-15T13:22:23Z</dc:date>
    </item>
  </channel>
</rss>

