yahoo-eng-team team mailing list archive

[Steve Martinelli <stevemar@xxxxxxxxxx>]

This is no longer an issue since the main use case was getting the ID
from middleware.

The kvs backend has been removed and forcing the templated backend to
have an ID is not necessary.

** Changed in: keystone
     Assignee: Steve Martinelli (stevemar) => (unassigned)

** Changed in: keystone
       Status: In Progress => Invalid

** Changed in: keystone
       Status: Invalid => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1326421

Title:
  No endpoint ID in v3 KVS or templated catalog

Status in OpenStack Identity (keystone):
  Won't Fix

Bug description:
  The v3 API specifies that endpoints appearing in the service catalog
  should have an ID [1].

  This patch finally introduced v3 support for the KVS and templated
  backends, but unfortunately does not address the lack of endpoint IDs
  [2]. Even in the case of the KVS and templated implementations, IDs
  should still be provided.

  [1] https://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3.md#tokens
  [2] https://review.openstack.org/#/c/70630/

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1326421/+subscriptions