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

Bug 1121843

Summary:	[RFE][keystone]: JSON Home
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	Nathan Kinder <nkinder>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ami Jeain <ajeain>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, ayoung, markmc, slong, trichard, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/json-home
Whiteboard:	upstream_milestone_juno-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-keystone-2014.2.1-1.el7ost	Doc Type:	Enhancement
Doc Text:	With this release, the Identity service now supports the standard JSON Home document format for API discovery. the service's previously supported API discovery response format was a non-standard JSON document. This format required a client to have Identity-specific knowledge to understand how to use the response. The JSON Home document format allows API discovery to use a standardized format, allowing client applications to perform API discovery across multiple services in a standard way.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 20:05:05 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 2014-07-22 04:06:04 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/json-home.

Description:

The server will return a JSON Home document for GET /v3, /v2.0, and / if the Accept header indicates to use application/json-home.


Specification URL (additional information):

https://github.com/openstack/keystone-specs/blob/master/specs/juno/json-home.rst

Comment 2 Scott Lewis 2015-02-09 20:05:05 UTC

This bug has been closed as a part of the RHEL-OSP 6 general availability release. For details, see https://rhn.redhat.com/errata/rhel7-rhos-6-errata.html