Bug 1563632

Summary: can't switch user when accessing the engine with an active kerberos ticket
Product: Red Hat Enterprise Virtualization Manager Reporter: Sandro Bonazzola <sbonazzo>
Component: ovirt-engineAssignee: Ravi Nori <rnori>
Status: CLOSED ERRATA QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: lsurette, mperina, rbalakri, Rhev-m-bugs, rnori, srevivo, ykaul
Target Milestone: ovirt-4.2.3   
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: 2018-05-15 17:48:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Martin Perina 2018-04-04 17:39:11 UTC
Ravi, switch user functionality is not related to authentication performed by Apache (Kerberos, SAML, CAS, ...), right? Switch user works only for username/password authentication within oVirt SSO, right?

Comment 4 Ravi Nori 2018-04-05 13:34:09 UTC
Posted a patch to fix the issue, the user should be able to switch user even with a valid Kerberos ticket.

Comment 5 Sandro Bonazzola 2018-04-05 14:30:00 UTC
(In reply to Ravi Nori from comment #4)
> Posted a patch to fix the issue, the user should be able to switch user even
> with a valid Kerberos ticket.

Can you please add the gerrit reference to this bug?
Looks like automation failed to do so.
Also, please open a ticket on oVirt infra about this, so they can fix it.

Comment 7 Petr Matyáš 2018-04-16 08:03:20 UTC
Verified on ovirt-engine-4.2.3-0.1.el7.noarch

I can now switch user on welcome page when I have an active SSO token and also I can switch back to SSO login with Next-Auth button on switch user page.

Comment 11 errata-xmlrpc 2018-05-15 17:48:31 UTC
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/RHEA-2018:1488

Comment 12 Franta Kust 2019-05-16 13:08:46 UTC
BZ<2>Jira Resync