I recently came across an issue that took some time trying to resolve regarding 802.1x configuration on ThinOS 9.1 that I wanted to share.
Ultimately, the issue came down to the SSL certificate name not matching the certificate name entered into the Wyse Management Suite (WMS) configuration.
When the device was trying to authenticate, it was using a certificate name that didn’t match what was in the WMS configuration and failed to authenticate because of this.
Some errors we received in the event log but weren’t very descriptive although it appeared to be a certificate authentication issue based on ‘private key passphrase needed for SSID’ error message.
- TLS: Failed to set TLS connection parameters
- EAP-TLS: Failed to initialize SSL
- WLAN: CTRL-REQ-PASSPHRASE-0:Private key passphrase needed for SSID
- WLAN: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)
We then looked at the WMS 802.1x configuration and verified the certificate name, in this case, ‘wyse.pfx’ – note the lowercase ‘w‘. We uploaded again to WMS and verified we got prompted for password so that looked correct.
We then looked at actual certificate we uploaded, ‘Wyse.pfx’, and made note of the case – capital ‘W‘ vs the lowercase ‘w‘ that was entered in WMS console so we changed WMS to match certificate name. We changed it from ‘wyse.pfx’ to ‘Wyse.pfx’. Once we did this and rebooted device, it connected to the network successfully!
Lesson learned, it’s never a bad idea to verify case sensitivity and try to make sure they match to avoid this potential pitfall!
Hope you found this helpful!
- More details on 802.1x configurations noted here
- If you are new to ThinOS 9.1, here is a quick video overview of some of it’s features.
- Looking for more details on ThinOS 9.1? Check out the release notes here
- Excellent Dell Wyse community located here
- Dell Community forums for ThinOS here
@chris_messier ~~> Subscribe to blog to get latest updates <~~