Bug 1023759 - [RFE] re-implement SSO solution based on JRS new SSO interface
Summary: [RFE] re-implement SSO solution based on JRS new SSO interface
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-reports
Version: 3.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.4.0
Assignee: Juan Hernández
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-27 16:31 UTC by Yaniv Lavi
Modified: 2014-02-07 13:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 10:36:28 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Yaniv Lavi 2013-10-27 16:31:54 UTC
Description of problem:
JasperReports Server has a new SSO interface that is committed to not break.
I order to pervert rebase issues it is needed to re-implement to the new interface.

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

Comment 1 Juan Hernández 2014-01-09 10:34:07 UTC
I have been looking at the information about the new authentication interfaces provided by Jasper. What I see there is that they provide mechanism to authenticate users with external systems, like LDAP, or custom systems. But this is something that happens *after* Jasper has asked the user for his credentials, so it isn't usable for SSO purposes. For SSO we need to tell Jasper to not ask for credentials, but to trust the ones already provided by the user to the oVirt portal. In these regards what they provide (according to the documentation) is
the "pre auth" filters. That is what we are using in the current SSO solution. So I would say that we don't need to change anything.

Comment 2 Yaniv Lavi 2014-01-09 10:36:28 UTC
Thanks Juan. Barak, I'm closing this case, since there isn't seem to be any update needed.



Yaniv


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