Forum Discussion
Why openNetworkConfiguration not working in enrolled device?
I have enrolled a device and want to use managed wifi on that device. I have used following configuration-
"openNetworkConfiguration": {
"Type": "UnencryptedConfiguration",
"NetworkConfigurations": [
{
"GUID": "inovex_wifi",
"Name": "INovex-Dev",
"Type": "WiFi",
"WiFi": {
"SSID": "INovex-Dev",
"Security": "WPA-EAP",
"EAP": {
"Outer": "EAP-TLS",
"Identity": "faruk",
"DomainSuffixMatch": ["dms.mobi-manager.com"],
"ServerCARefs": ["ca_inovex"],
"ClientCertType": "Ref",
"ClientCertRef": "client_inovex"
}
}
}
],
"Certificates": [
{
"GUID": "ca_inovex",
"Type": "Server",
"X509": "ca_base64"
},
{
"GUID": "client_inovex",
"Type": "Client",
"PKCS12": "client_base64"
}
]
}
My expection is
- This network automatically save in wifi list
- As I set client and server certificate the device should connect automatically
- For information I have used freeradius server for authentication.
3 Replies
- jeremyLevel 3.0: Honeycomb23 days ago
Hello,
So your configuration seems ok, but you might be missing the AutoConnect field set to true.
Have you tried with AutoConnect? the documentation is available here: https://developers.google.com/android/management/configure-networks make sure that all your fields are supported but it seems like it.
- mhfarukLevel 2.0: Eclair23 days ago
Thanks for your quick response. I have tried with AutoConnect field but same result. Couldn't understand the problem actually. Do you have any other idea?
- jeremyLevel 3.0: Honeycomb23 days ago
You can look at the device logs see if you can get some more details. But if the configuration is correctly applied, it might be an issue on your Wifi EAP side
Related Content
- 27 days ago
- 2 years ago
- 2 years ago