Bug#1006318: openconnect: failed to request VPN secrets #3: No agents were available for this request

Marco Marzetti

unread,

Feb 23, 2022, 7:30:03 AM2/23/22

to

Package: openconnect
Version: 8.20-1
Severity: important

Dear Maintainer,

After upgrading to openconnect and libopeconnect5 version 8.20-1, the dialog window with username and password no longer show up when you star the VPN from within nm-applet. While everything works with nmcli.

Here's the log messages i can see with journalctl:
Feb 23 12:48:29 lilith NetworkManager[762]: <info> [1645616909.6596] vpn[0x55c0afa0a0f0,83bffdb1-1077-4b5f-a691-90c89948b86a,"PCCWG IPE"]: starting openconnect
Feb 23 12:48:29 lilith NetworkManager[762]: <info> [1645616909.6600] audit: op="connection-activate" uuid="83bffdb1-1077-4b5f-a691-90c89948b86a" name="PCCWG IPE" pid=2358 uid=1000 result="success"
Feb 23 12:48:29 lilith NetworkManager[762]: <warn> [1645616909.7494] vpn[0x55c0afa0a0f0,83bffdb1-1077-4b5f-a691-90c89948b86a,"PCCWG IPE"]: secrets: failed to request VPN secrets #3: No agents were available for this request.

Everything works if i roll back to version 8.10-8.

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openconnect depends on:
ii libc6 2.33-6
ii libgnutls30 3.7.3-4+b1
ii libopenconnect5 8.20-1
ii libproxy1v5 0.4.17-1
ii libxml2 2.9.12+dfsg-6
ii vpnc-scripts 0.1~git20210402-1

Versions of packages openconnect recommends:
ii python3 3.9.8-1
ii python3-asn1crypto 1.4.0-1
ii python3-mechanize 1:0.4.7-1
ii python3-netifaces 0.11.0-1+b1

Versions of packages openconnect suggests:
ii bash-completion 1:2.11-5

-- no debconf information

--

Marco

Sergio Vavassori

unread,

Feb 23, 2022, 11:40:03 AM2/23/22

to

Package: openconnect
Followup-For: Bug #1006318
X-Debbugs-Cc: vava...@gmail.com

Dear maintainer,

I found this morning that upgrating to 8.20-1 introduced
a problem with Network-Manager applet.

The notification error message is "Unable to connect, no valid VPN secrets available"
while in syslog it reports: "failed to request VPN secrets #3: User canceled the secrets request."

I'm using SAML authentication.

Rolling back to 8.10-8 makes everything working again.

-- System Information:
Debian Release: bookworm/sid
APT prefers testing

APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)

Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT:it

Sergio Vavassori

unread,

Feb 24, 2022, 3:10:03 AM2/24/22

to

Package: libopenconnect5
Version: 8.20-1

Followup-For: Bug #1006318
X-Debbugs-Cc: vava...@gmail.com

After having done some tests, I found that the problem is in libopenconnect5 package since this configuration shows it.

ii libopenconnect5:amd64 8.20-1 amd64 open client for various network vendors SSL VPNs - shared library
ii openconnect 8.10-8 amd64 open client for Cisco AnyConnect, Pulse, GlobalProtect VPN

Regards

Luca Boccassi

unread,

Feb 27, 2022, 9:20:03 AM2/27/22

to

On Thu, 24 Feb 2022 09:05:57 +0100 Sergio Vavassori
<vava...@gmail.com> wrote:
> Package: libopenconnect5
> Version: 8.20-1
> Followup-For: Bug #1006318
> X-Debbugs-Cc: vava...@gmail.com
>
>
> After having done some tests, I found that the problem is in
libopenconnect5 package since this configuration shows it.
>
> ii libopenconnect5:amd64 8.20-

1 amd64 open client for various

network vendors SSL VPNs - shared library
> ii openconnect 8.10-

8 amd64 open client for Cisco

AnyConnect, Pulse, GlobalProtect VPN
>
>
> Regards

Have you updated network-manager-openconnect and network-manager-
openconnect-gnome to 1.2.6-4? Have you restarted
NetworkManager/rebooted since doing that?

--
Kind regards,
Luca Boccassi

signature.asc

Sergio Vavassori

unread,

Feb 27, 2022, 10:10:04 AM2/27/22

to

Il giorno dom 27 feb 2022 alle ore 15:13 Luca Boccassi <bl...@debian.org> ha scritto:

Have you updated network-manager-openconnect and network-manager-
openconnect-gnome to 1.2.6-4? Have you restarted
NetworkManager/rebooted since doing that?

Yesterday (it wasn't available before in testing) I updated network-manager-openconnect and network-manager-openconnect-gnome from 1.2.6-3 to 1.2.6-4 and that resolved the issue, no need to reboot.

From my side I consider the bug closed, thanks for the quick fix.

Regards,

Sergio