Wifi Enterprise (EAP/PEAP) not working with Android 13

Question

Hello, 
 we use Wifi Enterprise with Security type EAP/PEAP. 
 The configuration is working in the past but now the Wifi not connect after the enrollment of the device. 
 This error only occurs on Android 13 devices for about 3 weeks. 
 Has anything changed there? 
 
 Here is my configuration: 
 SSID = [SSID Wifi] 
 Security type = EAP/PEAP 
 Phase 2 authorization = MSCHAPv2 
 Identity = [user whos known on the RADIUS-Server] 
 Anonymous identity = %_USERNAME_% 
 Password = [Password from the Identity User] 
 Identity certificate = None 
 Trusted certificate = [Root certificate] 
 
 I can't see any Information for a connection request on the RADIUS-Server, when the Device is rolled out. 
 > The phone doesn't even try to connect with the Wifi. 
 
 Can anyone help me here?

Jan-Philipp Lechner · Accepted Answer

Hi ck-r , 
 it was the combination of the version 9.7.10218 and the domain suffix match of the certificate, by us. 
 We have TLS, but the android requirements are changed. At least I found something there. https://www.androidenterprise.community/t5/community-feedback/recent-android-change-regarding-wifi-configuration/td-p/359 
 Sophos support also pointed out the domain suffix name again. https://doc.sophos.com/central/Mobile/help/en-us/AdminHelp/Policies/AndroidEnterpriseDevice/WiFi/index.html 
 We had to fill the domain suffix match in the SCEP- and Wifi-Profile and with the version 9.7.10218 works all again.

Qoosh · Answer

This issue is resolved in version 9.7.102XXX and later of the SMC app. Allow me some time to inquire internally about the expected release date for this version and I will update you here. 
 Update: The new SMC client will roll out to customers on Monday, November 6th.

ck-r · Answer

Hi, 
 thanks for your answer. 
 It works too after insert the Domain suffix match.

Wifi Enterprise (EAP/PEAP) not working with Android 13

Top Replies