Bug 1041908 - [RFE][keystone]: OpenID connect as A Federated IdP protocol
Summary: [RFE][keystone]: OpenID connect as A Federated IdP protocol
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: Upstream M1
: 7.0 (Kilo)
Assignee: Nathan Kinder
QA Contact: Mike Abrams
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_kilo-1 upstream_st...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:01 UTC by RHOS Integration
Modified: 2016-04-26 16:58 UTC (History)
6 users (show)

Fixed In Version: openstack-keystone-2015.1.0-1.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-05 13:11:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 17:07:06 UTC

Description RHOS Integration 2013-12-12 20:01:18 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/openid-connect.

Description:

In order to provide the perspective an additional mechanism brings to the design approach, we are going to look into implementing OpenID connect, which has been used as a federation protocol comparable to, and different from SAML.  This document will capture the differences from the SAML implementation for extending the Federated approach.

Specification URL (additional information):

None
Comment 3 Mike Abrams 2015-03-20 09:39:06 UTC 
Nathan, need more on the success criteria here; i've read the full spec here but still feel i need some direction on how to test.  thx a lot.
Comment 11 errata-xmlrpc 2015-08-05 13:11:01 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://access.redhat.com/errata/RHEA-2015:1548
Note You need to log in before you can comment on or make changes to this bug.