Ubuntu
gnome-control-center package

VPN settings don't store user name for openconnect VPNs

Bug #1875806 reported by Martin Hierholzer on 2020-04-29

This bug report is a duplicate of: Bug #1838838: username is not saved in openconnect connection dialog. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-control-center (Ubuntu)	New	Undecided	Unassigned

Bug Description

Expected behavior:

When logging in to a openconnect-based VPN that has been setup through the network settings in the control center, there is an option to store the username and the password. When enabling this option while logging in, I expect the username (and the password in an obfuscated way) to be shown next time a login is attempted.

Observed behavior:

On the next login attempt, the user name field is empty. The password seems to be correctly stored - it shows the dots in the field and just filling in the user name allows to login.

Steps to reproduce:

1. Open gnome system menu (or how this is called - top right corner by default, where also the power-off switch is)
2. Select the "VPN off" entry, click "Connect"
3. A dialogue 'Connect to VPN "<name>"' appears with a box "Please enter your username and password."
4. Enter username and password, enable "Save passwords" and hit "Login".
5. The VPN connection is established.
6. Disconnect through the gnome system menu again ("Turn off")
7. Repeat steps 1. to 3. - The username field is empty.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 09:21:13 2020
InstallationDate: Installed on 2020-04-23 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Martin Hierholzer (mhier) wrote on 2020-04-29:

Screenshot of dialogue at step 3 on the second connect attempt Edit (25.8 KiB, image/png)
Dependencies.txt Edit (21.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (310 bytes, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2020-04-29:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1838838, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.