Skip to main content
Level 1.6: Donut
October 27, 2025
Question

Why openNetworkConfiguration not working in enrolled device?

  • October 27, 2025
  • 1 reply
  • 0 views

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 

  1. This network automatically save in wifi list
  2. As I set client and server certificate the device should connect automatically
  3. For information I have used freeradius server for authentication.

1 reply

Level 1.6: Donut
October 27, 2025

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.

mhfarukAuthor
Level 1.6: Donut
October 27, 2025

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?

Level 1.6: Donut
October 27, 2025

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