Esper supports several ways to connect managed devices to secured Wi-Fi networks, and the correct setup depends on both the device platform and the network's security type. This article helps you identify which configuration your network requires and points you to the article that covers it.
In this article
- Wi-Fi Security Types at a Glance
- Android Wi-Fi Authentication
- iOS Wi-Fi Authentication
- Linux Wi-Fi Authentication
- If Your Network Type Isn't Listed
Wi-Fi Security Types at a Glance
| Security type | Platform | Article |
|---|---|---|
| Open network (None), WEP, WPA/WPA2, WPA3-personal (SAE), EAP | Android | Managing Android Devices through a Blueprint |
| Open network (None), WEP, WPA/WPA2 | Android | Create a Wi-Fi Allow List |
| EAP-TLS (certificate-based) | Android | Configure Certificates Using a File Path or SCEP |
| PEAP (username and password) | Android | Not currently supported. Use EAP-TLS instead. |
| Open network (None), WEP, WPA, WPA2 | iOS/iPadOS/tvOS | Managing Apple Devices through Blueprints and Settings |
| PEAP (username and password, with root certificate) | iOS/iPadOS | Connecting an iOS Device to a PEAP Network |
| Open network (None), WPA2 (personal/PSK) | Windows | Managing Windows Devices through a Blueprint |
| Varies | Linux | Not Applicable |
Use the table to find your network's security type, then follow the linked article for platform-specific setup.
Android Wi-Fi Authentication
Android Wi-Fi configuration in Esper splits across two workflows, depending on how your network authenticates devices.
Open, WEP, and WPA/WPA2 networks
Use a Wi-Fi Allow List to add these networks to a blueprint, template (legacy), or through an API command. This is the entry point for most standard Android Wi-Fi setups, including networks that don't require certificate-based authentication. See Create a Wi-Fi Allow List for setup steps.
EAP-TLS (certificate-based) networks
If your network requires EAP-TLS, you'll need to push a certificate to the device before it can authenticate. Esper supports two certificate delivery methods:
- SCEP (Simple Certificate Enrollment Protocol), which enrolls the device for a certificate automatically.
- File Path, which pushes a certificate file to the device using Content Management, then references that file path in the blueprint's Wi-Fi configuration.
See Configure Certificates Using a File Path or SCEP for both methods, including the section on attaching a SCEP configuration to an EAP-TLS Wi-Fi network.
Note: This article is filed under certificate management, but it's the correct reference for Android EAP-TLS Wi-Fi setup, including certificate delivery through Content Management.
iOS Wi-Fi Authentication
Use a blueprint to configure iOS, iPadOs, or tvOS on open, WEP, WPA, or WPA2 networks.
iOS devices connect to PEAP networks using a configuration profile that combines a root certificate with username and password credentials. You build the profile in Apple Configurator or iMazing Profile Editor, then deploy it to the device through a blueprint's iOS settings.
See Connecting an iOS Device to a PEAP Network for the full walkthrough.
Windows Wi-Fi Authentication
Esper supports Wi-Fi configuration for Windows devices through the Blueprint Connectivity section (Windows tab). The supported security type is WPA2 (personal/PSK). Admins add access points by SSID, security type, and password, and can mark networks as hidden.
Linux Wi-Fi Authentication
Wi-Fi authentication on Linux devices is configured at the OS or image level, not through the console, and it needs to be working before provisioning because the agent requires outbound connectivity to enroll.
If Your Network Type Isn't Listed
If your Wi-Fi network uses a security type not covered above, or if you're troubleshooting a certificate that isn't reaching the device through Content Management, contact Esper Support with your network's security type and device platform.