Bug 851191 - RFE: Close spice console in case that user's right on object were deleted
RFE: Close spice console in case that user's right on object were deleted
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-userportal (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Einav Cohen
Pavel Stehlik
Depends On:
  Show dependency treegraph
Reported: 2012-08-23 09:15 EDT by Tomas Dosek
Modified: 2012-08-23 09:21 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-23 09:21:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Dosek 2012-08-23 09:15:45 EDT
Description of problem:
In case that user's on some object (vm, pool) were removed while user is connected to this VM/pool VM, the object should dissapear from User Portal of this User.

Another thing that should be done is to close the Spice/VNC/RDP window of user.

When we leave this window opened for the user it can be seen as a security issue in customers' point of view.

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

How reproducible:
100 %

Steps to Reproduce:
1. Create a VM/pool assign rights on this object to a user
2. Login to userportal using given user account and start the VM and connect to it
3. From webadmin remove user's rights on this object
Actual results:
Console stays opened

Expected results:
Object should dissapear from user's list of VMs and console should close immediately.

Additional info:
Comment 1 Itamar Heim 2012-08-23 09:21:15 EDT
user could have opened the spice not via user portal.
so correct behavior would be to send setvmticket to host to disconnect the spice session.
but even windows and linux won't log you off if your permission to login was revoked.

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