Bug 1334387 - [TEST ONLY] SAML Federation using Shibboleth
Summary: [TEST ONLY] SAML Federation using Shibboleth
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Adam Young
QA Contact: Rodrigo Duarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-09 13:36 UTC by Maxime Payant-Chartier
Modified: 2020-01-17 15:45 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-24 12:53:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1761 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 9 General Availability Advisory 2016-08-24 16:49:52 UTC

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
Note You need to log in before you can comment on or make changes to this bug.