configuring opencoonect VPN works OK. Trying to enable the connection switches the toggle button immediately to off. Instead of displaying credential window. NetworkManager logs include these lines: NetworkManager[3705]: <info> [1487307523.5305] audit: op="connection-activate" uuid="c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d" name="VPNCONN" pid=5455 uid=1000 result="success" NetworkManager[3705]: <info> [1487307523.5372] vpn-connection[0x25812d0,c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d,"Rutgers",0]: Started the VPN service, PID 5494 NetworkManager[3705]: <info> [1487307523.5443] vpn-connection[0x25812d0,c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d,"Rutgers",0]: Saw the service appear; activating connection NetworkManager[3705]: <error> [1487307523.5646] vpn-connection[0x25812d0,c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d,"Rutgers",0]: Failed to request VPN secrets #3: No agents were available for this request. NetworkManager[3705]: <info> [1487307523.5656] vpn-connection[0x25812d0,c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d,"Rutgers",0]: VPN plugin: state changed: stopped (6) NetworkManager[3705]: <info> [1487307523.5667] vpn-connection[0x25812d0,c8d70f1b-b3f3-4bcd-b634-d7a1ac69ae5d,"Rutgers",0]: VPN service disappeared using "nmcli --ask c u VPNCONN" properly asks for credentials but after frmLogin realm [Default|td_local]:Default frmLogin username: password: Connected to HTTPS on https://vpn.server it displays: Error: Connection activation failed: unknown reason. using openconnect manually from the commandline works OK # openconnect --juniper https://vpn.server ... frmLogin realm [Default|td_local]:Default frmLogin username: password: ... connected to HTTPS on vpn.server Connected as X.Y.Z.W, using SSL ESP session established with server I'm Using net-misc/openconnect-7.07-r2
downgrading to networkmanager-openconnect-1.2.2 fixes both GUI and cli way of activating VPN connections
I can confirm this bug. The really relevant error message is this one though: JS ERROR: error while enumerating VPN auth helpers: Gio.IOErrorEnum: Error opening directory '/etc/NetworkManager/VPN': No such file or directory To get VPN working again, one has to create this directory, and then put a symlink to the relevant .name file there: /etc/NetworkManager/VPN/nm-openconnect-service.name -> /usr/lib/NetworkManager/VPN/nm-openconnect-service.name
(In reply to Andreas Grois from comment #2) > I can confirm this bug. > The really relevant error message is this one though: > > JS ERROR: error while enumerating VPN auth helpers: Gio.IOErrorEnum: Error > opening directory '/etc/NetworkManager/VPN': No such file or directory > > To get VPN working again, one has to create this directory, and then put a > symlink to the relevant .name file there: > /etc/NetworkManager/VPN/nm-openconnect-service.name -> > /usr/lib/NetworkManager/VPN/nm-openconnect-service.name thanks, the fix works for me.
*** Bug 609314 has been marked as a duplicate of this bug. ***
The file needs to be there because gnome-shell wasn't ported yet out of old libnm-glib: https://bugzilla.redhat.com/show_bug.cgi?id=1394977 https://bugzilla.redhat.com/show_bug.cgi?id=1398425 The creation of this file should be fixed then with -r1 (at least, it seems to work for me). If still getting some failures, maybe you are then facing a bug like bug 609732 [master d4bf576] net-misc/networkmanager-openconnect: We cannot drop libnm-glib support yet (--without-libnm-glib) because gnome-shell wasn't ported yet (#609594, also https://bugzilla.redhat.com/show_bug.cgi?id=1394977 and https://bugzilla.redhat.com/show_bug.cgi?id=1398425). 1 file changed, 49 insertions(+) create mode 100644 net-misc/networkmanager-openconnect/networkmanager-openconnect-1.2.4-r1.ebuild
