The free ride of just putting in your username and password in Android is over. If you need to do this on a large scale, you would need software or a utility that automatically sets up your android devices to download your CA certificate and correctly installs the supplicant.
For a detailed explanation about the change see here:
https://www.securew2.com/blog/android-11-server-certificate-validation-error-solution (ClearPass has this through its Onboard Module).
The latest version of Android requires that the CA certificate be installed on the Android device and the supplicant be properly configured.
If you go ahead with software that automatically configures mobile devices, you might as well go to EAP-TLS, which is more secure than eap/peap
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
HPE Design and Deploy Guides:
https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card------------------------------
Original Message:
Sent: Nov 21, 2022 06:18 PM
From: Huda Abbasi
Subject: Android devices cert issues
Hi all,
I am having trouble getting Android devices connected to my school district's secured Wifi, it uses PEAP with MSCHAPV2. The issue started showing up since Android OS 10. Devices used to be able to connect by selecting "Do not check" for CA. Now that option is no longer working and I can't figure out what I need to do to get those devices authenticated. The option to "Trust on first use" worked for a while then it no longer worked even if you forget the network, but even when it did work it was only temporary.
I'm new to this job and our previous person who set this all up left without enough documentation on how he set it up.
Any help or tips are greatly appreciated!
Thank you!