SUMMARY
An openconnect network connection configured to automatically connect to a VPN will completely break and not allow you to connect again if you cancel (or fail) out of the VPN login prompt.

This seems very similar to bug 340543.

STEPS TO REPRODUCE
1. Configure a network to automatically connect to a VPN.
2. Connect to the network (I do so by logging out then logging back in)
3. Wait for the VPN secrets dialog to open, then cancel it (or wait a few minutes for the login timeout to be reached)

OBSERVED RESULT
The network connection fails, and if you try to connect back to the network a connecting spinner is momentarily displayed before canceling out. Also, the VPN connection is not visible in the Networks list.

EXPECTED RESULT
The network connection should fail, but selecting "Connect" should restart the connection process including opening the VPN secrets dialog and requesting the user to sign in.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.9-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I upped the severity because this can occur whenever the network needs to reauthenticate. For example, when my device is locked & unlocked, I am disconnected from the network & VPN, and will need to reauthenticate. If I fail or cancel the authentication process then I cannot reconnect to the network until I either log out and back in, or reboot, losing my session state. Finally, I haven't been able to verify this just yet, but this problem may have caused me issues where I could not connect to *any* network, not just the one I initially connected to, when the VPN secrets dialog timed out, but I need to verify this another day.

This might just be a NetworkManager bug.