SUMMARY Gateway:port, user name, password and trusted certificate in "Advanced" settings provided correctly, but no respnse whe I click on "Connect" - does not do anything. However, as a workaround, "openfortivpn" works flawlessly from the command line! STEPS TO REPRODUCE 1. Add a VPN conncetion based on fortisslvpn, put in credentials. 2. "Apply" / "OK". 3. "Connect" in Network Manager. OBSERVED RESULT Nothing going on. EXPECTED RESULT Should establish the VPN connection. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed (current upgrade), kernel 5.11.4-1 (available in About System) KDE Plasma Version: 5.79.0-1.2 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION openSUSE Tumbleweed, latest version (25.03.2021).
I confirm the issue. It is caused by the 2fa-flags configuration added by plasma-nm. See here: https://bugs.archlinux.org/task/69749
Created attachment 137082 [details] attachment-6648-0.html Thanks for the info! --B. Scheichl On Friday, 26 March 2021 09:59:52 CET Pedro de Carvalho Gomes wrote: > https://bugs.kde.org/show_bug.cgi?id=434940 > > Pedro de Carvalho Gomes <pedrogomes81@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |pedrogomes81@gmail.com > > --- Comment #1 from Pedro de Carvalho Gomes <pedrogomes81@gmail.com> --- > I confirm the issue. It is caused by the 2fa-flags configuration added by > plasma-nm. See here: https://bugs.archlinux.org/task/69749 -- Priv.-Doz. DI Dr. Bernhard Scheichl Technische Universität Wien | Institute of Fluid Mechanics and Heat Transfer Tower BA/E322 | Getreidemarkt 9 | 1060 Vienna | Austria T: +43-1-58801-32225 | www.fluid.tuwien.ac.at<http://www.fluid.tuwien.ac.at/>
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-nm/-/merge_requests/53
The bug is caused by unnecessary empty 2fa values that are added to the .nmconnection file when the "2FA" is left unchecked. This empty values are used downstream, and if the openfortivpn client doesn't support it, it will complain and terminate. At the simple fix, now plasma-nm doesn't store the 2fa garbage is the checkbox is not set.
Git commit 2876e7f38a53b5c615b64bd7ff91289002cb5d6d by Jan Grulich, on behalf of Pedro Gomes. Committed on 29/03/2021 at 05:45. Pushed by grulich into branch 'master'. Fix bug with openfortivpn that do not support 2fa M +0 -2 vpn/fortisslvpn/fortisslvpnwidget.cpp https://invent.kde.org/plasma/plasma-nm/commit/2876e7f38a53b5c615b64bd7ff91289002cb5d6d
Git commit 13bc2023b8a7c3070cc45b83b3120197de0e69b1 by Jan Grulich, on behalf of Pedro Gomes. Committed on 29/03/2021 at 05:57. Pushed by grulich into branch 'Plasma/5.21'. Fix bug with openfortivpn that do not support 2fa M +0 -2 vpn/fortisslvpn/fortisslvpnwidget.cpp https://invent.kde.org/plasma/plasma-nm/commit/13bc2023b8a7c3070cc45b83b3120197de0e69b1
It's worth pointing out that the fix won't have effect with existing connections that had the bad "2fa" values. Either the person removes the garbage manually, or delete and create a new connection.