Getting PanGPS to work in GNOME

Ask Fedora
1

Hi,

I’m trying to make a VPN connection (GNOME) using Palo Alto Networks GlobalProtect protocol to work. No luck and getting the following outputs:

$ sudo journalctl -f

20:45:20 fedora NetworkManager[1557]: <info>  [1739990720.9294] vpn[0x563320874390,0092ac46-32d8-4b4a-8093-335208bd2ea0,"EN"]: starting openconnect
20:45:20 fedora NetworkManager[1557]: <info>  [1739990720.9300] audit: op="connection-activate" uuid="0092ac46-32d8-4b4a-8093-335208bd2ea0" name="EN" pid=22691 uid=1000 result="success"
20:45:22 fedora rtkit-daemon[1438]: Failed to look up client: No such file or directory
20:45:22 fedora rtkit-daemon[1438]: Successfully made thread 35574 of process 35546 (/usr/libexec/webkit2gtk-4.1/WebKitWebProcess) owned by '1000' RT at priority 5.
20:47:21 fedora NetworkManager[1557]: <warn>  [1739990841.0717] vpn[0x563320874390,0092ac46-32d8-4b4a-8093-335208bd2ea0,"EN"]: secrets: failed to request VPN secrets #3: No agents were available for this request.

Checking keyring:

$ systemctl --user status gnome-keyring-daemon

● gnome-keyring-daemon.service - GNOME Keyring daemon
     Loaded: loaded (/usr/lib/systemd/user/gnome-keyring-daemon.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Wed 2025-02-19 20:10:18 EET; 38min ago
 Invocation: f2ab271b6dd34f34bde1a7881b1e1565
TriggeredBy: ● gnome-keyring-daemon.socket
   Main PID: 19889 (gnome-keyring-d)
      Tasks: 6 (limit: 38102)
     Memory: 3M (peak: 4M)
        CPU: 184ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-keyring-daemon.service
             ├─19889 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
             └─22512 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh

20:10:18 fedora systemd[2439]: Started gnome-keyring-daemon.service - GNOME Keyring daemon.
20:10:18 fedora gnome-keyring-daemon[19889]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring
20:10:18 fedora gnome-keyring-daemon[19889]: The PKCS#11 component was already initialized
20:10:18 fedora gnome-keyring-d[19889]: The PKCS#11 component was already initialized
20:10:18 fedora gnome-keyring-daemon[19889]: The Secret Service was already initialized
20:10:18 fedora gnome-keyring-d[19889]: The Secret Service was already initialized
20:10:50 fedora gnome-keyring-daemon[19889]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
20:10:50 fedora gnome-keyring-d[19889]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered

When restarting NetworkManager:

$ sudo journalctl -f -u NetworkManager

20:54:15 fedora NetworkManager[38797]: <info>  [1739991255.5886] device (wlo1): Activation: (wifi) access point 'Sand_5G' has security, but secrets are required.
20:54:15 fedora NetworkManager[38797]: <info>  [1739991255.5898] device (wlo1): Activation: (wifi) connection 'Sand_5G' has security, and secrets exist.  No new secrets needed.

SAML login works and I seem to get the cookie needed. But then something breaks with the secrets. Not quite sure what is going on, any pointers? System is fresh 41, just installed and updated. Thanks in advance…

2

This looks like the first thing to fix.

3

You can use the following option in the connection settings:

  • Store the password for all users

This should eliminate the need to query agents.