I think you are right here about the way the passwords are stored, and that is why you cannot do EAP-TTLS. - Thanks for, what I consider, confirmation 🙂
EAP_TLS would be a nightmare in this scenario Im affraid 🙂
The customer has some, fun requirements, about onboarding should be easy, and then they want "credentials stored".
I mean, sure, in theory you could "store" your credentials in the browser for the splash-login page on an open (OWE) network, but the end-user would have to login more times (citation needed), because of mac-randomization.
Splash-access "dorm" solution using iPSK is really nice, a good interface (like Cisco really should build into ISE for iPSK with Radius). But iPSK without radius does not work with WPA3, and we really want WPA3 (because of 6Ghz). Of course WPA3 iPSK with Radius should work, but then we come back to students needing to find their mac-address, and .... from what I can tell, they are not capable of such things, and it would give a large workload on their support team.
We could fairly easy provide the students with a onboarding script WLAN profile for windows and MAC computers, and then use EAP-TTLS (where the client would then of course store the credentials), and for mobile devices use TOFU. But EAP-TTLS is off the table because of Entra External ID.
iPSK without radius regardles of WPA3 , would still be easy for the dorms, and "ok".
But for the actual education sites, Im thinking (right now, because of the above requirements), WPA3-SAE for the "base" student SSID (so that the device does not change its mac), and then a splashpage.
Is this a annoying solution, yes .... yes it is ... but its perhaps the only thing thats possible giving the customers requirements and their ... "obsession" of using Entra External ID for students.
Of course we could also just go plain WPA3-SAE, and not needing "identity" ... would be the easiest 🙂
Thanks to all for your replies.
Thomas