NetworkManager-openconnect issues would be at
https://gitlab.gnome.org/GNOME/NetworkManager-openconnect but most of the hard
thinking ends up on the openconnect side.
So what is the best solution here? The external browser mode is useful
because we get the fully features of Chrome/Firefox and
I don't think this is an openconnect issue? Or are you handling network
manager issues there too? I see the Ubuntu patch was merged upstream
since this was opened?
"External browser" would be nice, but IT says we can't turn it on, needs
some upgrade, and CISCO says not to use it:
The saml
https://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect410/release/notes/release-
notes-
anyconnect-4-10.html#Cisco_Reference.dita_07f4a7eb-b660-4a09-844c-c3ed481aebc0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can we take this to https://gitlab.com/openconnect/openconnect/-/issues
please?
I think you want to enable the "external browser" support which we added
in OpenConnect 9.01.
cf.
Upon more research it seems there is alot more wrong here than the
misleading message from Duo.
GTK Webkit completely lacks support for webauthn, so it is pointless to
think about anything at the network-manager-openconnect level. This
means this will not support security tokens for VPN login.
