Created attachment 152382 [details] Openconnect settings page for Fortinet SUMMARY I'm unable to use the Fortinet's protocol provided by OpenConnect. I usually connect to the job's vpn with username and password and a token sent by email after login. When configuring such VPN connection there is any field for username and password so the plugin tries to use a certificate file that, in my case, is not provided. I can normally use openconnect from command line: sudo openconnect --protocol=fortinet MY-GATEWAY --user MY-USERNAME STEPS TO REPRODUCE 1. Open Connections Manager Settings 2. Add a "VPN Compatible Fortinet (openconnect)" 3. Edit settings OBSERVED RESULT No imput fields for username and password EXPECTED RESULT Fields for username and password SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION
Does creating a "Fortinet SSLVPN (fortisslvpn)" connection work as expected? Not sure why both "Fortinet SSLVPN (fortisslvpn)" and "Fortinet Compatible VPN (openconnect)" exist. I suspect it's the same kind of VPN but exposed via two different "backends"
(In reply to Nicolas Fella from comment #1) > Does creating a "Fortinet SSLVPN (fortisslvpn)" connection work as expected? > Not sure why both "Fortinet SSLVPN (fortisslvpn)" and "Fortinet Compatible > VPN (openconnect)" exist. I suspect it's the same kind of VPN but exposed > via two different "backends" "Fortinet SSLVPN (fortisslvpn)" partially works in the sense that I can receive on my mail the OTP but the window in which I should write it up stays open for a blink. I reported the bug here https://bugs.kde.org/show_bug.cgi?id=436158. Thanks
Bulk transfer as requested in T17796