FS#70733 - [plasma-nm] usergroup not forwarded for openconnect VPN
Attached to Project:
Arch Linux
Opened by Aaron Barany (akb825) - Thursday, 06 May 2021, 07:12 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 06 May 2021, 08:54 GMT
Opened by Aaron Barany (akb825) - Thursday, 06 May 2021, 07:12 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 06 May 2021, 08:54 GMT
|
Details
Description:
When specifying a usergroup for the VPN gateway (in the form vpn.company.com/usergroup), the usergroup is used for the initial login through the dialog, but not forwarded to NetworkManager for the actual VPN connection. This causes the VPN connection to either fail or register as connected and not work properly. Additional info: * Upstream bug ticket: https://bugs.kde.org/show_bug.cgi?id=435561 * Upstream commit to fix the issue: https://github.com/KDE/plasma-nm/commit/8f37efe9696fc5aa42d789c5259edf8a8d866c5f The fix is currently on the master branch, so it will likely be incorporated in the next major release. (5.22) Steps to reproduce: 1. Connect to a VPN with a usergroup in the gateway address. 2. Initial login through the dialog succeeds. 3. After the initial login, NetworkManager will either fail to establish the subsequent connection or it won't work properly. |
This task depends upon
Comment by Antonio Rojas (arojas) -
Thursday, 06 May 2021, 07:29 GMT
Comment by Aaron Barany (akb825) -
Thursday, 06 May 2021, 08:43 GMT
That commit is in 5.21.5, which version are you using?
You're right, double checking the Plasma/5.21 branch it looks like
it was cherry-picked across. Sorry, I thought I checked but I
guess I didn't look hard enough.