Bug 1168314

Summary: Add python-pysaml2 dependency to openstack-keystone to enable federation
Product: [Fedora] Fedora Reporter: Nathan Kinder <nkinder>
Component: openstack-keystoneAssignee: Alan Pevec <apevec>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: apevec, apevec, bfilippov, dennis, itamar, jonathansteffan, jose.castro.leon, lhh, nkinder, notting, p, rbryant
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-keystone-2015.1.0-3.fc23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1233856 (view as bug list) Environment:
Last Closed: 2015-06-19 19:26:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1232186    
Bug Blocks: 1233856    

Description Nathan Kinder 2014-11-26 16:22:07 UTC
The latest openstack-keystone package for the upstream OpenStack Juno release has an extension that requires the pysaml2 python package (https://pypi.python.org/pypi/pysaml2).  We need to create a python-saml2 RPM for pysaml2 to allow Keystone's federation extension to work.

Comment 1 Alan Pevec 2014-11-26 16:29:47 UTC
I'll create Fedora review for pysaml and make this bz depend on it.

Comment 2 Alan Pevec 2015-03-31 08:34:04 UTC
pysaml2 installs multiple top-level modules, not sure why is not everything under saml2, if they're used only by saml2 ?
 s2repoze
 saml2
 xmldsig
 xmlenc

Comment 3 Alan Pevec 2015-03-31 09:26:06 UTC
At least xmldsig is conflicting with https://pypi.python.org/pypi/xmldsig and will need to be treated as vendorized library.

Comment 4 Alan Pevec (Fedora) 2015-04-03 16:52:16 UTC
Upstream is going to move top-level modules: https://github.com/rohe/pysaml2/issues/202

Comment 5 Fedora End Of Life 2015-05-29 13:24:06 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.