Meraki Wifi Authentication Using Okta Fails (EAP-TTLS)
Last Updated:
Integrations
Okta Classic Engine
Multi-Factor Authentication
Okta Identity Engine
Overview
The New Cisco Meraki Wi-Fi (EAP-TTLS) fails via the Okta RADIUS client. A connection cannot be established because the certificate is not valid and/or trusted by the device.
Applies To
- Cisco Meraki Wireless LAN (RADIUS)
- Okta RADIUS Agent
Cause
When an admin manually installs a cert for EAP-TTLS, it may not be configured correctly to be trusted by the device. The 802.1x profile is not being deployed properly.
Solution
Deploying an 802.1x profile that holds the certificate through Apple Configurator 2 will resolve this issue.
NOTE: Some users may try to deploy the profile through JAMF or manually and this may fail. So it is recommended to deploy the profile with the certificate through Apple Configurator 2 as this has been confirmed to work.
