network-manager-openconnect doesn't work with new nm-connection-editor

Status changed to 'Confirmed' because the bug affects multiple users.

Any guidance on how to manually build network-manager-openconnect? I downloaded it ok, but there's no instructions...I tried ./configure, but lots of dependencies that put me off.

I found this on the logs:

/var/log/syslog

Apr 22 09:48:13 laptop dbus-daemon[768]: Unknown username "nm-openconnect" in message bus configuration file

$ grep -i nm /etc/passwd
nm-openvpn:x:123:131:NetworkManager OpenVPN,,,:/var/lib/openvpn/chroot:/bin/false
nm-openconnect:x:122:130:NetworkManager OpenConnect plugin,,,:/var/lib/NetworkManager:/bin/false

A guidance how to manually build it you can find here (but only in german):
https://forum.ubuntuusers.de/topic/openconnect-networkmanager-funktioniert-nicht/

Translated in english (as far as I can):

http://tomtomtom.org/networkmanager-openconnect/

NOTE: Just a workaround, not a permanent fix!

https://wiki.gnome.org/Projects/NetworkManager/VPN says this:

"Plugin compatibility note

NetworkManager generally gets released together with the new versions of VPN plugins. However, it maintains backward compatibility with older plugin versions. That means that the plugin version 0.9.10.0 will work with later NetworkManager versions, such as 1.2.

There's one exception to this: the editor plugins were ported to new libnm library in NetworkManager 1.2. The older version of the library can not coexist in a single process. Thus, the newer libnm-based nm-connection-editor will not be able to edit the VPN connections unless you also upgrade the VPN plugin."

The last paragraph explains the issue -- the plugin will work with the new NetworkManager but nm-connection-editor will not be able to edit VPN connections.

I can create and edit connections in Gnome from the network settings GUI it just does not connect when I enter my Username and PASSCODE in the Connection window.
No error message or similar it just doesn't connect.

I confirm deere's post: can edit, add or delete openconnect VPN connections from NetworkManager, but, when I login, I get an error message saying that it couldn't connect. But this connection used to work perfectly well until the upgrade.

Julien, please see bug #1575354 for the bug that it sounds like you are encountering, and please provide debug logs there if possible.

This bug is about the inability to create or edit OpenConnect VPN connections, which will be fixed with an updated version 1.2.0.

Any users affected by this bug can test network-manager-openconnect 1.2.0-1, which is now in the yakkety-proposed repository. This version of the package should fix the errors reported here, please confirm.

The updated packages are now released in the yakkety repository, marking as fixed.

If you would like to see these packages backported to Ubuntu 16.04, please take a look at the procedure for requesting a stable release update at https://wiki.ubuntu.com/StableReleaseUpdates, and file a new bug to do so.

Will do so. Thx, for your efforts!

I've tested the packages from Yaketi and they work for me.

The same issue applies to network-manager-strongswan package on ubuntu 16.04.

It is also a problem for network-manager-ssh and network-manager-iodine.

--
Tiger!P
A random quote:
What was not spoken of did not have te be lied over.

I confirm that the packages from yakketi repository works for me.

As noted by reply #11, I'd like to request a Stable Release update for this fix, however, I am not sure I fully understand the process to complete that request. I am not a developer. I do use Ubuntu but now, cannot remote connect to my office because of this bug. How do I see if a request has already been submitted?

Hi,

I installed the yakkety package:

$ apt-cache policy network-manager-openconnect
network-manager-openconnect:
  Installed: 1.2.0-1build1
  Candidate: 1.2.0-1build1
  Version table:
 *** 1.2.0-1build1 500
        500 http://mx.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.0.2-1build1 500
        500 http://mx.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

but openconnect is not yet showing up in network-manager, should I also install netwotk-manager from yakkety?

To use the graphical interface you need to install the network-manager-openconnect-gnome plugin, too.

And be carefull with yakkety-repos in your xenial system.

ahhh, thanks tomtomtom, I can now see the openconnect option in the GUI, but now it complains about the CA file, though my vpn does not use a CA file.. still unusable for me..

Same problem with Xubuntu 16.04

It is the same package so it is the same issue. All *buntus uses the same repos.

You will find the bigfix above.

Hi all,

Can someone confirm that a request for a SRU has been submitted on this bug for 16.04?

Thanks!

Tried and submitted SRU for 16.04
https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1579284

Upgraded both packages(Ubuntu 16.04, just DL from YY repo & installed 2 packages)

apt-cache policy network-manager-openconnect*

network-manager-openconnect-gnome:
  Installed: 1.2.0-1build1
  Candidate: 1.2.0-1build1
  Version table:
 *** 1.2.0-1build1 100
        100 /var/lib/dpkg/status
     1.0.2-1build1 500
        500 http://mirror.timeweb.ru/ubuntu xenial/universe amd64 Packages
network-manager-openconnect:
  Installed: 1.2.0-1build1
  Candidate: 1.2.0-1build1
  Version table:
 *** 1.2.0-1build1 100
        100 /var/lib/dpkg/status
     1.0.2-1build1 500
        500 http://mirror.timeweb.ru/ubuntu xenial/universe amd64 Packages

I confirm that now I can add & edit Cisco Annyconnect type connections, but still is unable to connect, on connection attempt I see the following error in syslog:

final secrets request failed to provide sufficient secrets

While I'm able to connect using plain openconnect CLI, just providing host, authgroup, username & password.(no additional keys or options are required). Maybe another bug?

Yes, the bug about the impossibility to connect to the VPN is there: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1575354

Maybe one of those bugs should be marked as a duplicate of the other...

Looks like we need network manager 1.2. We're stuck at 1.1.93 until 1.2 gets out of -proposed. Right now 1.2 in -proposed is broken, see:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/comments/19

on closer inspection, it looks like everything is in progress here:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726
network manager 1.2 will have to go first, then the -openconnect plugin will go. Please follow bug #1576726 so that you can test the proposed package once it is available.