Bug 1055566

Summary:	[RFE] Allow configuration of vnc password timeout and alphabet
Product:	[Retired] oVirt	Reporter:	Sven Kieske <s.kieske>
Component:	ovirt-engine-webadmin	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	3.3	CC:	ecohen, gklein, iheim, mgoldboi, michal.skrivanek, rbalakri, s.kieske, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-29 09:06:25 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 Sven Kieske 2014-01-20 14:38:53 UTC

Description of problem:

when you open a vnc session with a vm the default timeout
of this is 2 minutes and can't be configured anywhere.
The value seems to be hardcoded

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
can't configure vnc password timeouts

Expected results:

can configure the password timeout via webadmin and possibly via REST-API
and SDK.
additional: maybe configure password value (alphabet to use and how strong the password should be)

Additional info:

This would be a great enhancement for dev systems where you have to use
vnc very much.

Comment 1 Itamar Heim 2014-01-21 19:30:45 UTC

just a note that i think this is supported via the REST API

Comment 2 Sven Kieske 2014-01-27 10:05:03 UTC

You can generate a "ticket" via api and specify the expiration time. 
But you can not do this via webadmin, this should be resolved when
webadmin uses rest as backend.

Comment 3 Michal Skrivanek 2014-02-25 16:34:18 UTC

Can you please detail why would I be using the password manually typing it on the cmdline instead of hacking up a script which does that for me?
For misc stuff there's REST API so I don't really see much benefit having an option in webadmin which is supposed to be a bit more simple
I'm not against it, I just don't see the need

Comment 4 Sven Kieske 2014-02-25 16:52:29 UTC

(In reply to Michal Skrivanek from comment #3)
> Can you please detail why would I be using the password manually typing it
> on the cmdline instead of hacking up a script which does that for me?
> For misc stuff there's REST API so I don't really see much benefit having an
> option in webadmin which is supposed to be a bit more simple
> I'm not against it, I just don't see the need

Well this RFE is not just about one thing, so let's split it up:

1. Make the timeout configurable via UI

I know I can do this via API, so why not make it accessible via UI?
There might be situations where you got no REST-Client OR CLI available.

In DEV setups you may have to frequently check things inside vms with vnc
or spice. If you can't set the expiration via API as described above you
will always have to click another time for getting a new password, every 2
minutes.

2. Make the used characterset for the password generation configureable

Currently I don't know how the passwords get generated, but they might
yield characters which can't be typed on certain keyboard layouts
(I can't tell if that is the case because I do not know how it gets generated)

All in all, I do not need this functionality anymore myself, because I can
always use the API.

But I can imagine other people might not want or can't use it (the API).
So I figured out this would be a cool improvement for their needs.

But maybe I'm wrong with that, you decide.

Comment 5 Michal Skrivanek 2014-02-26 11:13:05 UTC

well, patches welcome, but I do see this quite a low prio.
Let's keep it open if someone want to pick it up

Comment 6 Itamar Heim 2015-03-29 09:06:25 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.