MDM pushing wrong identity value to Android phones for EAP-TLS

MR45EOL
Here to help

MDM pushing wrong identity value to Android phones for EAP-TLS

Trying to setup certificate based authentication on phones. After battling with using Windows CA and UPN and Microsoft coming changes feb 2025 using secure options we gave up using unique user certifcates and accepted using the same cert for all users.

 

But even after accepting that defeat I cant get Android to work. iPhones behave as expected and provides the correct value as identity/username when connecting and connect fine to the WiFi. Android phones however picks the value/number from the Common Name of the default Meraki SCEP-certificate called "SCEP" in the dropdown. Doesnt matter that you change to your own cert payload in the dropdown under "Identity Certificate"

 

Have a case open with Meraki support but cant seem to get them to agree on that this has to be a bug in the Meraki MDM interface? You can easily edit the saved SSID and change the identity field from the common name numbers to the username and connect fine to the wireless. It just seems that Meraki chooses the value from the wrong certificate.

0 Replies 0
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels