Agreed all around, it'd be really nice if there were better general standards for friendly ways to deploy and utilize 802.1x. IOT is definitely a big hold up th

Agreed all around, it'd be really nice if there were better general standards for friendly ways to deploy and utilize 802.1x. IOT is definitely a big hold up there, support is quite spotty even amongst new major device manufacturers. I recently was asked to deploy a bunch of Nest smoke alarms at a business for example (they are genuinely nice, and the testing I've seen indicate their dual wavelength photoelectric sensors do a very good job), and they don't support it. But even outside of IOT I'm quite surprised sometimes by mainstream devices that make it more of an effort then it needs to be, such as Chromebooks. I was surprised mainly because one place user/pass auth for WiFi isn't at all uncommon is colleges, and I'd have assumed students there were a significant enough general market to be worth more attention. On a Mac 802.1x is all a single flow at the simplest level, select the network, enter the credentials, it'll ask about the cert if it's self-signed, and that's it. Compare to the Chromebook procedure [1], it's not like it's horribly involved but why the whole separate cert procedure? Granted, authentication in general remains a lot of spaghetti across the entire industry. I don't think there is a lot of relief overall on the horizon, though at least in some areas like with WebAuthn there is hopeful progress. Maybe progress in separate areas will ultimately make a foundation that can be further expanded. 1: https://support.google.com/chromebook/answer/1047420?hl=en https://support.google.com/chromebook/answer/1047420?hl=en