Env: all KDE components are from Debian unstable, only plasma-nm is built from master (v5.9.95-3-g743fec5a). When new OpenConnect (Juniper) connection is created, plasma-nm sets the vpn.data protocol=juniper, which is incompatible with the rest nm tools. And vice-versa. If connection is created by nm-connection-editor, it sets protocol=nc, which isn't recognized by plasma-nm. Please make sure to stay compatible with the rest of nm tools.
Created attachment 105727 [details] Proposed patch
Git commit 7fe2a9622b24667cd5ad1c78e85fae9b4e14e264 by Jan Grulich. Committed on 30/05/2017 at 07:13. Pushed by grulich into branch 'master'. Openconnect (juniper): Make sure we are compatible with the rest of nm tools M +1 -1 vpn/openconnect/plasmanetworkmanagement_openconnect_juniperui.desktop https://commits.kde.org/plasma-nm/7fe2a9622b24667cd5ad1c78e85fae9b4e14e264
Git commit e52c259c2e7ca52b27c23aef6c018c579600e4b2 by Jan Grulich. Committed on 30/05/2017 at 07:13. Pushed by grulich into branch 'Plasma/5.10'. Openconnect (juniper): Make sure we are compatible with the rest of nm tools M +1 -1 vpn/openconnect/plasmanetworkmanagement_openconnect_juniperui.desktop https://commits.kde.org/plasma-nm/e52c259c2e7ca52b27c23aef6c018c579600e4b2
Thank you for considering this report! I'm not sure why you omitted the first part of the patch though. For me it seems that with current code the protocol=nc dataMap would become protocol=anyconnect in d->vpninfo. Which is most probably not a desired effect. Could you please take a closer look at this part of the code?
You are right, I didn't realize that. I'll fix it.