Bug 1334387

Summary: [TEST ONLY] SAML Federation using Shibboleth
Product: Red Hat OpenStack Reporter: Maxime Payant-Chartier <mpayantc>
Component: openstack-keystoneAssignee: Adam Young <ayoung>
Status: CLOSED ERRATA QA Contact: Rodrigo Duarte <rduartes>
Severity: high Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: jdennis, jjoyce, jmelvin, kbasil, nkinder, racedoro, rduartes, sclewis, sgordon, srevivo
Target Milestone: gaKeywords: FutureFeature, TestOnly, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-24 12:53:49 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:

Description Maxime Payant-Chartier 2016-05-09 13:36:13 UTC 
Description of problem:

Keystone has had SAML Federation support for some time now.  This functionality needs to be tested.  From an end user perspective, this includes:

- Using SAML to authenticate to Horizon via it's WebSSO functionality
- Using SAML ECP to authenticate to Keystone via the 'openstack' CLI
- Using one RHEL OSP cloud to authenticate to another RHEL OSP cloud (K2K)

This is the implementation using Shibboleth as a backend instead of RH-SSO
Comment 1 John Dennis 2016-05-09 13:51:52 UTC 
Maxime, why is Shibboleth being specified instead of RH-SSO?
Comment 2 Maxime Payant-Chartier 2016-05-09 18:11:41 UTC 
This is the bug that will be used to track the Shibboleth implementation,
The RH-SSO one will be on bug: https://bugzilla.redhat.com/show_bug.cgi?id=1263009
Comment 5 Stephen Gordon 2016-07-20 12:50:32 UTC 
Any updates here Basil?
Comment 8 Adam Young 2016-07-29 17:18:52 UTC 
This is a test only bug.
Comment 18 errata-xmlrpc 2016-08-24 12:53:49 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://rhn.redhat.com/errata/RHEA-2016-1761.html