https://bugs.kde.org/show_bug.cgi?id=362729

            Bug ID: 362729
           Summary: Cannot connect to OpenConnect VPN with
                    username/password
           Product: plasma-nm
           Version: 5.6.3
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: applet
          Assignee: jgrul...@redhat.com
          Reporter: jchevar...@gmail.com
                CC: lu...@kde.org

I am having trouble using plasma-nm to connect to an openconnect VPN. The
connection works fine when using the command line openconnect. It is
username/password auth based (so just url/gateway + username/password). When
connecting via plasma-nm, I do not get an authentication popup to enter my
credentials. 

>From the connection log on the GUI (note IP/endpoints are redacted):

POST https://x.y.z/
Attempting to connect to server 1.1.1.1:443
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
Got HTTP response: HTTP/1.1 302 Found
GET https://x.y.z/
Attempting to connect to server 1.1.1.1:443
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
Got HTTP response: HTTP/1.1 302 Found
GET https://x.y.z/dana-na/auth/url_default/welcome.cgi
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
XML response has no "auth" node



Reproducible: Always

Steps to Reproduce:
1. Create new openconnect VPN connection
2. Enter Gateway of x.y.z
3. Save
4. Go to Connect
5. Press connect button
6. Connection Error

Actual Results:  
Notification Popup:  Necessary secrets for the VPN connection were not
provided.

In log: XML response has no "auth" node

Expected Results:  
I would expect a username/password authentication dialog to popup and then have
the VPN Connection created.

I am on Arch Linux with the latest testing packages - QT 5.6.0, Frameworks
5.21.0, Plasma 5.6.3.

Both networkmanager and networkmanager-openconnect are version 1.2.0.

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

Reply via email to