Editing connection settings takes very long to open

[raleik-pl]

Running latest release on Ubuntu 26.04 and Gnome 50.
When clicking on a gear icon in Gnome VPN settings, to edit an existing connection, this is what I get:

It is spinning like that for around 25 seconds! until I finally get to edit the parameters.
Meanwhile, immediatelly after clickng the gear, this is what is printed in journalctl:

Jul 20 15:20:27 <hostname> gnome-shell[5973]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
                                                 _vpnRequest@resource:///org/gnome/shell/ui/components/networkAgent.js:829:22
                                                 _handleRequest@resource:///org/gnome/shell/ui/components/networkAgent.js:806:18
                                                 _newRequest@resource:///org/gnome/shell/ui/components/networkAgent.js:801:18
                                                 @resource:///org/gnome/shell/ui/init.js:20:20
Jul 20 15:20:52 <hostname> gnome-control-center[30181]: Failed to get secrets: Timeout was reached

[WMP]

That 25 s hang is a missing VPN auth-dialog. When you open the connection, gnome-shell's secret agent tries to launch an auth dialog for the plugin, but the released .name file declares none — so _vpnRequest throws the unhandled rejection you see, the agent never answers, and NetworkManager only gives up after its 25 s secrets timeout (Failed to get secrets: Timeout was reached), which is when the editor finally opens.

This is fixed on the feat/interactive-auth-issue-6 branch: it ships a proper auth dialog (/usr/libexec/nm-gpclient-auth-dialog, in the -gnome package) and declares it in the service .name file, so the agent gets an immediate answer instead of hanging.

Same test build as in #7: https://github.com/WMP/GlobalProtect-SAML-NetworkManager/actions/runs/29749216928 — please give it a try and let me know if the editor opens instantly.

[raleik-pl]

Hi,
thanks for the followup on this.
The window now loads much faster, the spin only shows for few seconds now and then it's ready.
I see this now in journalctl

Jul 24 12:00:56 raleik-laptop gnome-control-center[11136]: Failed to get secrets: User canceled the secrets request.

Which I believe is how you handle that with own shorter timeout?

[WMP]

Not intentional, no — that line was a bug of its own, just a much less annoying one than the 25 s hang.

A SAML connection has no stored secrets at all, and the auth dialog was exiting with an error code to say so. NetworkManager reports that to whoever asked as "user canceled the secrets request", which is the line you saw. The dialog now answers with an empty secret set and exit code 0, so the editor opens immediately and the journal stays quiet.

Same build as in #7 if you want to confirm the log is clean:
https://github.com/WMP/GlobalProtect-SAML-NetworkManager/actions/runs/30215509759