| Summary: | [openconnect] not successful after valid credentials are provided | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Bernhard Schmidt <bschmidt> |
| Component: | Networking in general | Assignee: | Jan Grulich <jgrulich> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bschmidt, chgonzalezg, dns_hmpf, emailmeat, jgrulich, keplicz, thiago |
| Priority: | NOR | ||
| Version: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/plasma-nm/0ebb1756a5a6c2cb56032fffa6153e6283dc42b0 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: | Patch to fix openconnect issue | ||
|
Description
Bernhard Schmidt
2017-05-29 05:55:55 UTC
I experience the same bug but am running KDE neon User Edition 5.10 (16.04). I noticed the problem this morning after I ran the upgrade to 5.10 yesterday. The following error I see from journalctl -f -u NetworkManager.service: Failed to request VPN secrets #3: No agents were available for this request. Via nmcli I get a working VPN connection as well. This is probably restricted to openconnect as another vpn connection with vpnc works. I unfortunately don't have access to any openconnect vpn to be able to test it. I did check all changes in plasma-nm which made it to Plasma 5.10, but I don't think any of them could break openconnect plugin, but everything is possible. Is anyone willing to give me access to your openconnect server, i.e. with limited access or with a testing user, I wouldn't really take advantage of this, but without out that I'm afraid I won't be able to do something about this. Alternatively you can try to build plasma-nm from Plasma/5.9 branch so we identify whether this is a bug introduced in Plasma 5.10. You will notice you are using older versions because the dialogs asking for secrets are different. *** Bug 380400 has been marked as a duplicate of this bug. *** Sorry, can't provide any access. I'm not in control of the server side and I'd like to not give out creds of my account. :S I did some bisecting on the plasma/5.10 branch. Commit e5574b4 seems to have broken it, f5c9a67 is working fine. openconnect seems to do the auth but somehow the creds and/or the xmlconfig stuff isn't given back to plasma-nm? Not sure how all this is supposed to work, pointers on how to debug from here are welcome. :) Created attachment 105816 [details]
Patch to fix openconnect issue
I have identified a potential problem caused be the above mentioned commit. Can anyone verify whether this patch fixes this issue?
(In reply to Jan Grulich from comment #5) > Created attachment 105816 [details] > Patch to fix openconnect issue > > I have identified a potential problem caused be the above mentioned commit. > Can anyone verify whether this patch fixes this issue? yes, it does fix it. Connection up and running :) Thanks! Git commit ebfbe93510d7e5a10992a482efe38bc934dd19c5 by Jan Grulich. Committed on 01/06/2017 at 10:33. Pushed by grulich into branch 'master'. Openconnect: make sure we accept the dialog M +7 -1 vpn/openconnect/openconnectauth.cpp https://commits.kde.org/plasma-nm/ebfbe93510d7e5a10992a482efe38bc934dd19c5 Git commit 0ebb1756a5a6c2cb56032fffa6153e6283dc42b0 by Jan Grulich. Committed on 01/06/2017 at 10:33. Pushed by grulich into branch 'Plasma/5.10'. Openconnect: make sure we accept the dialog M +7 -1 vpn/openconnect/openconnectauth.cpp https://commits.kde.org/plasma-nm/0ebb1756a5a6c2cb56032fffa6153e6283dc42b0 Thanks, 5.10.1 works great! *** Bug 381133 has been marked as a duplicate of this bug. *** *** Bug 381158 has been marked as a duplicate of this bug. *** *** Bug 380938 has been marked as a duplicate of this bug. *** Bulk transfer as requested in T17796 |