Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1041908

Summary:	[RFE][keystone]: OpenID connect as A Federated IdP protocol
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	Nathan Kinder <nkinder>
Status:	CLOSED ERRATA	QA Contact:	Mike Abrams <mabrams>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ayoung, markmc, nbarcet, nkinder, nlevinki, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA, Triaged
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/openid-connect
Whiteboard:	upstream_milestone_kilo-1 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-keystone-2015.1.0-1.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:11:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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