Bug 1705711

Summary:	Save passwords doesn't remember realm or username
Product:	[Fedora] Fedora	Reporter:	Robert Hollencamp <rhollencamp>
Component:	NetworkManager-openconnect	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	30	CC:	code, dcbw, dwmw2, iq5lz5plhik, mattias.ellert, nmavrogi, rdieter, thaller
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-08 06:15:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Robert Hollencamp 2019-05-02 19:40:38 UTC

Description of problem:
I have an OpenConnect (Juniper/Pulse) VPN configured in network manager; when connecting, it will open a dialog box to collect realm, username, and password. There is a checkbox to remember these credentials, but only the password itself is remembered.


Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Configure an openconnect juniper/pulse VPN
2. Start connection
3. Enter credentials, select 'save passwords', and connect
4. Disconnect and then reconnect

Actual results:
password is remembered, but realm and username need to be re-entered


Expected results:
connection to the VPN is completed without having to prompt for anything


Additional info:
this worked on previous versions of fedora

Comment 1 iq5lz5plhik 2019-07-04 19:51:31 UTC

Second that. Previously seen on Fedora 24 and not until Fedora 30. References:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1609700
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=bb45adeda0bf427ada23b09daf970b0757e82d60

Comment 2 David Woodhouse 2019-08-07 10:04:31 UTC

I think this is the same as bug #1332491

Comment 3 David Woodhouse 2019-08-08 06:15:26 UTC


*** This bug has been marked as a duplicate of bug 1332491 ***