Bug 1251000 - [RFE][user portal] allow sso for non-spice console (would bring feature to non-x86_64 hw)
[RFE][user portal] allow sso for non-spice console (would bring feature to no...
Status: CLOSED DEFERRED
Product: ovirt-engine
Classification: oVirt
Component: Frontend.UserPortal (Show other bugs)
---
Unspecified Unspecified
unspecified Severity low (vote)
: ---
: ---
Assigned To: bugs@ovirt.org
Pavel Stehlik
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-06 07:55 EDT by Jiri Belka
Modified: 2017-03-13 03:45 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-13 03:45:27 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
ylavi: ovirt‑future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)

  None (edit)
Description Jiri Belka 2015-08-06 07:55:40 EDT
Description of problem:

with BZ1149594 we got pam and gdm-plugin rhevm-guest-agent rpm for ppc64. unfortunatelly SSO is hardcoded only in spice console connect.

as ppc64 do not have spice console (no qxl, i have no idea now) they must have VNC console. so we got rpms for guest agent to enable sso but user portal code is limited to issue sso login only for spice. this doesn't make much sense then.

so as we get working agent, pam and gdm module, let's test if sso could work on ppc64. iiuc there's no reason why it should not work.

Version-Release number of selected component (if applicable):
ovirt-engine-userportal-3.6.0-0.0.master.20150804111407.git122a3a0.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. have directory client setup working in x86_64 spice vm
2. have directory client setup working in ppc64 vnc vm
3. add domain (ipa, openldap) to engine, assing domain user to the vms
4. initialize console opening from user portal for x86_64 and see if there would be SSO (iirc, DesktopLogin command in vdsm.log)
5. do the same for ppc64 vm

Actual results:
ppc64 sso does not work as there's no instruction from backend to vdsm to issue DesktopLogin (?)

Expected results:
there should be no technical issues why SSO could not work on vnc consoles

Additional info:
Comment 1 Yaniv Kaul 2017-03-13 03:45:27 EDT
Not aware of customer requests for this, closing for the time being.

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