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.
Description of problem:
When signed in as user in katello, switching to foreman, logging out and logging in as new user, returning to katello will remain logged in as the first user.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Login as admin user to /katello
2. Create new user, "fibble"
3. Navigate to Provisioning
4. Logout admin user
5. Login as fibble
6. Navigate to Content; view name of logged in user
Actual results:
Logged in user is still admin
Expected results:
Logging out from UI should logout across all portions of unified UI
User should not be able to exist as previously logged-in user in other portions of UI.
Additional info:
I think this is a regression? I'm fairly (though not 100%) sure this worked before.
I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=969886
The question is, do we want some bigger changes to Katello and Signo to support this even when Signo won't be used in future? There's still a quick and dirty way to achieve logout - we could just delete user session cookies but since Katello uses cookie store session there may be data that we should not delete.
So can't we just say that this is a known "feature" of current version which will be changed later?