[plasma-nm] [Bug 448153] Unable to access the VPN network in double authentication mode (anyConnect SAML/SSO)

2022-01-09 Thread David Woodhouse
https://bugs.kde.org/show_bug.cgi?id=448153

David Woodhouse  changed:

   What|Removed |Added

 CC||dw...@infradead.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 363917] [RFE] Add Juniper support for OpenConnect VPN

2016-07-06 Thread David Woodhouse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363917

--- Comment #1 from David Woodhouse <dw...@infradead.org> ---
We did this differently in the end, but the above-referenced GNOME bug still
describes it.

In the short term, to just support *connecting* to a Juniper network and not
necessarily *configuring* one, we mostly just need to support the
NM_OPENCONNECT_KEY_PROTOCOL field and call openconnect_set_protocol() with its
contents.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma-nm] [Bug 363917] New: [RFE] Add Juniper support for OpenConnect VPN

2016-06-03 Thread David Woodhouse via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363917

Bug ID: 363917
   Summary: [RFE] Add Juniper support for OpenConnect VPN
   Product: plasma-nm
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: dw...@infradead.org
CC: jgrul...@redhat.com

We now have support for Juniper 'Network Connect' in
NetworkManager-openconnect. It is implemented as a separate top-level VPN
service 'org.freedesktop.NetworkManager.openconnect.nc' as discussed at 
https://bugzilla.gnome.org/show_bug.cgi?id=767197

We need support for adding/configuring the VPN, and for authenticating (which
is all basically the same as the existing AnyConnect support).

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.