Bug 421743

Summary: Realm option missing when connecting to Jumper/Pulse VPN via OpenConnect and NetworkManager.
Product: [Applications] systemsettings Reporter: akb825 <akb825>
Component: kcm_networkmanagementAssignee: Jan Grulich <jgrulich>
Status: RESOLVED NOT A BUG    
Severity: normal CC: plasma-bugs
Priority: NOR    
Version: 5.18.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description akb825 2020-05-18 20:59:55 UTC 
SUMMARY
Realm option missing when connecting to Juniper/Pulse VPN via OpenConnect and NetworkManager. For example, my company's VPN offers a "standard" connection that routes some traffic through the VPN and "tunnel-all" connection that routes all traffic. I am unable to select "tunnel-all" since the field is now missing.

STEPS TO REPRODUCE
1. Add a Juniper/Pulse OpenConnect VPN connection.
2. Connect to the VPN.

OBSERVED RESULT
Realm combo box option is missing.

EXPECTED RESULT
Realm combo box option is present.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
GNOME had the same issue as shown in this bug report: https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/issues/5. This may provide some insight on what may be causing the problem on KDE.
Comment 1 akb825 2021-04-09 23:16:25 UTC 
From what I can tell, the method of specifying the connection has changed in the VPN itself.

The realm was passed as a form parameter previously, which was able to be parsed to create a combo box in the UI. However, this is now provided with the usergroup parameter rather than the form. In other words, the information to display the UI is no longer being passed when connecting, and the usergroup parameter must be passed explicitly instead.

Unfortunately there appears to be no way to actually set the usergroup, so I'm still stuck unable to choose the "tunnel-all" connection type. I have created a separate bug (https://bugs.kde.org/show_bug.cgi?id=435561) to capture this issue.