Bug 1389241

Summary: [Docs][Intro to User Portal] [VMM] Login screen does not have 'auto connect' check box anymore
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: DocumentationAssignee: Emma Heftman <eheftman>
Status: CLOSED CURRENTRELEASE QA Contact: Megan Lewis <melewis>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: adahms, bugs, gklein, jbelka, lbopf, lsurette, melewis, michal.skrivanek, rbalakri, srevivo, tjelinek, ykaul, ylavi
Target Milestone: ovirt-4.0.7   
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: 2017-03-01 14:10:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Belka 2016-10-27 09:14:32 UTC
Description of problem:

Login screen does not have 'auto connect' check box anymore. I could not find any info about this change, thus here it is.

If it is by design, and I suppose yes, then understand this BZ as a bureacratic one to cover this change.

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

How reproducible:
100%

Steps to Reproduce:
1. Try to login to User Portal
2. is there checkbox for auto connect (ie. to have a console opened automatically after login)?
3.

Actual results:
the checkbox is missing

Expected results:
should be there

Additional info:
but the feature still works, ie. UP does automatically open console based on following conditions: the user has a VM assigned and _only_ one VM is running, then a console of this only running VM will be opened. if two VMs are running, then no console is opened - this is OK.

Comment 1 Jiri Belka 2016-10-27 09:28:07 UTC
In (per-user) Options, there's 'Connect Automatically' checkbox now. Thus this BZ can be closed with info that place where this feature is configured has moved.

Comment 2 Michal Skrivanek 2016-10-28 04:58:32 UTC
That was indeed done in 4.0 as part of infra's SSO feature. It should have been documented there, it may be in progress....worth checking. Which docs did you check?

Comment 3 Jiri Belka 2016-11-16 08:26:04 UTC
A(In reply to Michal Skrivanek from comment #2)
> That was indeed done in 4.0 as part of infra's SSO feature. It should have
> been documented there, it may be in progress....worth checking. Which docs
> did you check?

At least /docs/manual/en_US/html/Introduction_to_the_User_Portal/Logging_in_to_the_User_Portal1.html still mentions this checkbox.

Comment 4 Tomas Jelinek 2016-11-18 12:00:39 UTC
Right, changing to documentation issue.

In "Introduction to the User Portal" it is stated that:
"If you have only one running virtual machine in use, optionally select the Connect Automatically check box to connect directly to your virtual machine."

which is not true anymore. Since 4.0. this "connect automatically" chackbox is in "options" dialog, not on login screen.

Comment 6 Lucy Bopf 2016-12-22 02:21:51 UTC
Assigning to Emma for review.

Emma, this should simply involve removing all references to the "connect automatically" check box on the login screen, including screen captures that include the check box.

The new placement of the check box - in the 'Options' dialog in the User Portal - should be documented, if it has not already been.

Comment 7 Emma Heftman 2017-01-31 17:40:53 UTC
Tomas, please clarify how this feature works as the documentation in the Introduction Guide seems to imply that the feature only works if there is ONE running VM, however, the tooltip in the Edit Options window refers to connecting to the FIRST running VM.

So, can there be more than one running VM when the user logs in for this feature to work? If yes, please specify what is meant by "the first one"?

Does it mean furthest to the left of the window/the vm that has been running the longest?

Also, the tooltip mentions "if overt-engine has the user's password" but in what situation would we not know the user's password if he must always log in to the system?

Comment 8 Tomas Jelinek 2017-02-08 10:16:03 UTC
(In reply to emma heftman from comment #7)
> Tomas, please clarify how this feature works as the documentation in the
> Introduction Guide seems to imply that the feature only works if there is
> ONE running VM, however, the tooltip in the Edit Options window refers to
> connecting to the FIRST running VM.

okey, this is a bit confusing. There has to be exactly 1 VM to which it is possible to connect.
e.g. if you have 30 VMs down and 1 UP, than the connect automatically will open console to this one running VM. But, if you had 2 running VMs, than it would not open any console.

> 
> So, can there be more than one running VM when the user logs in for this
> feature to work? If yes, please specify what is meant by "the first one"?
> 
> Does it mean furthest to the left of the window/the vm that has been running
> the longest?
> 
> Also, the tooltip mentions "if overt-engine has the user's password" but in
> what situation would we not know the user's password if he must always log
> in to the system?

If the user uses Kerberos SSO than we don't get it. In other situations (e.g. filling name/password in the login form) we have it and can use it.