Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
During an impersonation session, a user with administrator privileges for Satellite can impersonate another user with administrator privileges and can perform all actions that an administrator performs including creating and deleting other users with administrative privileges.
Administrator should be able to look at how the app works under different user account without knowing their password. In user list, we can add a new "Impersonate" button that switches the account. User should see that the "impersonate" session is active in top bar end then just cancel it, restoring original user session. The impersonation should be logger as well as create an audit.
(In reply to Roman Plevka from comment #9)
> please, provide a proper documentation of the feature,
Hi Roman,
The product documentation changes are tracked in BZ#1778825, where I created a new procedure 'Impersonating a Different User Account' in the Administering Red Hat Satellite guide (for Satellite 6.7). The procedure is based on the scenario described in the Aha card: "As an admin user I can impersonate another user".
It is stated in the procedure that "Administrators can impersonate other authenticated users for testing and troubleshooting purposes". The situation you are describing in Comment #8 is indeed worrying, while the feature behaviour extends beyond 'testing and troubleshooting purposes'.
I agree with your assessment, this is not a scenario that we want to allow. However, I also believe that a programmatic solution to prevent this behaviour from occurring must be implemented.
What do you think?
> what are the expected
> outcomes with scenarios similar to the one described in Comment #8?
I will speak with our Content Strategists and Docs Program Manager to define the correct expectation for Comment #8 from a documentation point of view. I will update the ticket once I have more information.
Thank you.
Kind regards,
Vlada
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1454