Bug 1422801 - GA should not unlock screen if it is not locked
Summary: GA should not unlock screen if it is not locked
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-guest-tools
Version: 4.1.0
Hardware: Unspecified
OS: Windows
medium
medium
Target Milestone: ovirt-4.1.1
: ---
Assignee: Lev Veyde
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-16 09:51 UTC by Vinzenz Feenstra [evilissimo]
Modified: 2017-04-25 01:12 UTC (History)
10 users (show)

Fixed In Version: rhev-guest-tools-iso-4.1-4
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Previously, the guest agent tried to unlock the screen even if it was unlocked.This triggered the Secure Attention Sequence and opened a window prompting the user to change the password, lock the screen, and so on. This issue has now been resolved for most use cases.
Clone Of: 1365925
Environment:
Last Closed:
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1063 0 normal SHIPPED_LIVE rhev-guest-tools-iso bug fix and enhancement update 2017-04-18 20:59:26 UTC

Description Vinzenz Feenstra [evilissimo] 2017-02-16 09:51:24 UTC
+++ This bug was initially created as a clone of Bug #1365925 +++

Description of problem:

If disconnect action is NONE and console is closed then GA won't receive external command to lock-screen. But on next console opening GA still mimics ctrl-alt-del as part of login which causes an user would see SAS screen even he would expect to be logged in automatically.

The user could click 'Cancel' or hit 'Escape' but this is still little bit annoying.

Thus GA should check when doing login if the screen is or not locked.

Version-Release number of selected component (if applicable):
RVT 4.0-5 GA 56d5da5792258de810189e75b47d75806d1ef3b

How reproducible:
100%

Steps to Reproduce:
1. Windows 7 with GA and SSO configured on 4.0 host which sends correctly NONE for disconnectAction
2. check that SSO works fine by default, close console
3. change VM's settings disconnectAction to NONE
4. open newly console so disconnectAction settings is sent to vdsm
5. see you got automatically logged in
6. close console
7. open console

Actual results:
after 6. the screen is not locked but after 7. the user is not logged in automatically as he needs to type Esc or click Cancel

Expected results:
after 7. he should be automatically logged in

Additional info:

--- Additional comment from Michal Skrivanek on 2016-08-11 09:05:57 CEST ---

isn't it what "Single Sign On method" does?

--- Additional comment from Vinzenz Feenstra [evilissimo] on 2016-08-11 09:07:40 CEST ---

(In reply to Michal Skrivanek from comment #1)
> isn't it what "Single Sign On method" does?

The current SSO code does not check that

Comment 1 Jiri Belka 2017-04-12 22:45:08 UTC
ok, wgt 4.1-5


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