GNOME Bugzilla – Bug 624939
Should auto-detect EAP authentication type
Last modified: 2020-11-12 14:29:52 UTC
This bug was reported as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586858 In talking with someone who uses wpa-supplicant directly to connect to a WPA-EAP-protected network, they asked why NetworkManager needs to ask for the EAP authentication type (TTLS, PEAP, etc), and why it needs to ask for the inner authentication type. Apparently, wpa-supplicant can autodetect all of those from an EAP configuration packet. It certainly would make connecting to WPA networks easier if NetworkManager could autodetect this as well (or let wpa-supplicant do so) <dcbw> mbiebl: yes, that's possible. what we need to do on the NM side is allow more than one EAP configuration in a connection <dcbw> mbiebl: like Mac OS X and windows have basically checkbox lists that allow you to enable any number of EAP methods for a certain network <dcbw> mbiebl: that means you still get to *configure* the methods you want to allow <dcbw> mbiebl: but after having done so, we'd be able to connect to a network that might offer TTLS in one location and PEAP in another
Reopen if still applicable.
(In reply to comment #1) > Reopen if still applicable. Is this supposed to be fixed?
It should have been marked OBSOLETE, sorry. Your report is against an old version and nobody has replied for a long time. Please test with a recent version and we can reopen it.
I don't know why this was closed as obsolete, but it still exists in current NetworkManager. Setting up an EAP connection still requires manually specifying the authentication type.
Any updates on this?
Created attachment 374197 [details] Dialogue box proposed for a new connection
Created attachment 374198 [details] Dialogue box of eduroam
I have a working connection to eduroam. 374197 attachment shows the fields proposed when I connect to it as a new connection. 374198 attachment shows the fields as they should be to have a working connection. We can see that Authentication is identical in both cases (I do not know if this is because Tuneled TLS is chosen by default or if it was discovered). As for Inner authentication, it is different: it proposes MSCHAPv2 (no EAP), whereas it should be PAP. I use network-manager 1.14.4-4 in debian. HTH
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).