Bug 411177

Summary: VPN password is not displayed even if store passwords is checked
Product: [Applications] systemsettings Reporter: danielee0707
Component: kcm_networkmanagementAssignee: Jan Grulich <jgrulich>
Status: RESOLVED FIXED    
Severity: normal CC: 9luty1992, bartoszka1996, gudvinr+kde, jgrulich, mario.volf
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description danielee0707 2019-08-22 15:39:30 UTC 
SUMMARY
Openconnect VPN password in the VPN secrets panel is not displayed even if store passwords is checked. This behavior occurs when the first line of the prompt is GROUP rather than Username. The password entry can be found in kwalletmanager, however.

STEPS TO REPRODUCE
1. Add a new openconnect (anyconnect compatible) vpn in system settings. (But it may not be specific to openconnect as reported by other redditors.)
2. Add a Gateway that is consist of multiple groups.
3. Click connect for the new vpn in the system tray network icon.
4. Check automatically start connecting next time and store passwords. and click the connect cable icon next to vpn host.
5. Enter username and password and login.
6. Disconnect the vpn and try to reconnect. 

OBSERVED RESULT
The prompt window only shows saved Username in the second line. The first line is GROUP and can be selected. And to the right of the second line, an eye symbol indicates that this line is being recognized as Password, while in this case it should be the third line.

EXPECTED RESULT
Both the Username and Password are shown, and the eye symbol appears in the third password line.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION
Comment 1 prangija 2019-08-29 09:36:32 UTC 
I can confirm that I'm experiencing the same issue. The password is not being remembered and another weird issue is that "Username" field has an "eye" icon with tip stating "Change the visibility of the password". This is should be in the "Password" field and is clearly a bug.
Comment 2 baatochan 2019-09-11 14:05:15 UTC 
I can confirm that this may be wider issue as I noticed that for some time (a month) NetworkManager stopped saving my password. 
There is no entry in KWallet (wifi passwords are saved normally). 
I don't use a VPN (openconnect) with GROUP line. Only passcode to the key and username with password. The same as for others only the username is saved.
I also noticed that adding a new vpn doesn't help (with different name). 
OpenVPN is affected for me as well, because secrets provided during connection creation are lost after saving this new connection (just empty boxes are shown). Can't test connection as I don't have any working OpenVPN connections.
Comment 3 gudvinr+kde 2019-09-14 22:46:40 UTC 
Can confirm as well. I have L2TP and OpenVPN connection and both ask for password when you try to connect. When I look to kwallet there's no saved VPN passwords

KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.1
Comment 5 prangija 2019-10-17 10:31:49 UTC 
Am I the only one who still has this issue?
I have the latest versions of KDE Plasma (5.17) and network manager (1.20.4), but I'm still facing the same issues (password is not being remembered and username field has the "hide" icon instead of password field).
Comment 6 Jan Grulich 2019-10-18 11:00:33 UTC 
(In reply to prangija from comment #5)
> Am I the only one who still has this issue?
> I have the latest versions of KDE Plasma (5.17) and network manager
> (1.20.4), but I'm still facing the same issues (password is not being
> remembered and username field has the "hide" icon instead of password field).

Is this for Openconnect?
Comment 7 prangija 2019-10-18 11:23:31 UTC 
Yes, I have issues with Openconnect VPN connections. I can't be sure for others as I'm using just Openconnect currently.
Comment 8 prangija 2019-10-24 05:25:19 UTC 
Anyone? I can't be the only one still experiencing this.
Comment 9 prangija 2019-11-14 08:27:35 UTC 
This was finally solved for me by some of the latest upgrades of KDE frameworks (5.64) or Plasma (5.17.3).