Bug 1840165

Summary:	Password protected VNC should connect automatically
Product:	[Community] Virtualization Tools	Reporter:	Aldis Berjoza <aldis>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, crobinso, gscrivan, mhicks
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-15 19:47:11 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 Aldis Berjoza 2020-05-26 13:51:18 UTC

Description of problem:
If host has password protected VNC, when opening VNC password input is requested.
This really shouldn't be the case, because virt-manager can easily discover password from host configuration.

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


How reproducible:
Create host with password protected VNC. Don't store VNC password in keyring

Steps to Reproduce:
1. Open VNC connection
2. 
3.

Actual results:
virt-manager asks for a password

Expected results:
virt-manager uses password in configuration to automatically connect to password protected VNC session

Additional info:

Comment 1 Cole Robinson 2020-08-31 18:11:49 UTC

That's an interesting idea, thanks for the suggestion. It won't work in all cases though. vnc password could be from SASL or libvirt/qemu.conf which will not be reflected in the XML. So in theory keyring support is still valid. But we could pre-populate the UI from the XML if password is in plaintext. I wouldn't want to autologin because users would probably complain that password isn't working as expected.

Comment 2 Cole Robinson 2020-09-15 19:47:11 UTC

We are closing this bugzilla tracker for upstream virt-manager issues and moving to github. I filed your issue there: https://github.com/virt-manager/virt-manager/issues/153