Bug 362729

Summary:	[Openconnect] Cannot connect to OpenConnect VPN with username/password
Product:	[Plasma] plasmashell	Reporter:	Joe <jchevarley>
Component:	Networks widget	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED FIXED
Severity:	normal	CC:	jgrulich, lukas
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Joe 2016-05-06 02:22:26 UTC

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.

Comment 1 Jan Grulich 2016-06-06 13:45:40 UTC

I'm not able to reproduce this issue. I tried to setup an ocserver with plain user/password authentication and it works just fine. I guess that what you see in the log could be the reason why it doesn't work for you and I think that the problem is in the server you are trying to connect to.

Comment 2 Joe 2016-10-04 02:52:28 UTC

It works just fine using the command line openconnect tool, though, which would make me think its not the server. I believe the no auth return is from the fact that the username/password dialog never appears, and thus it always sends the connection request with no authentication particulars.

Comment 3 Jan Grulich 2016-10-04 05:44:51 UTC

Provide please information requested here:
https://techbase.kde.org/Projects/Solid/Plasma-nm#Plasma-nm_doesn.27t_remember_my_password

Comment 4 Joe 2016-11-16 19:29:06 UTC

So, I think this actually might be a misunderstanding. I use openconnect on the command line, but with the --juniper switch. Digging around a bit more, I want to say that the plasma nm applet doesn't actually support juniper yet - is that correct? Perhaps this should be more of a feature request issue.

Comment 5 Jan Grulich 2016-11-18 06:16:03 UTC

The support for Openconnect Juniper has been added to Plasma/5.8 (I think). There should be a new entry in the connection editor for that.

Comment 6 Joe 2016-11-23 06:21:56 UTC

Meant to update/comment - looks like it isn't in 5.8 - maybe its something for 5.9?

Comment 7 Jan Grulich 2016-11-23 06:29:15 UTC

Hm, I didn't realize it was pushed to master only so it will be released with Plasma 5.9, see bug 363917.

Comment 8 Joe 2016-11-23 17:57:15 UTC

Ah, perfect appreciate it, for some reason I couldn't find a bug for it existing (although I did see something about it in the mailing lists). Thanks!

Comment 9 Joe 2017-06-14 18:28:06 UTC

So that bug didn't fix this issue for me, but, 380399 finally has, which is awesome.

Comment 10 Ben Cooksley 2024-12-23 18:25:59 UTC

Bulk transfer as requested in T17796