Bug 1840165 - Password protected VNC should connect automatically
Summary: Password protected VNC should connect automatically
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 13:51 UTC by Aldis Berjoza
Modified: 2020-09-15 19:47 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-15 19:47:11 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.