Public bug reported:
For some project, such as Cinder, the endpoint is project specified, the format
is like:
http://ip/volume/v3/{project_id}/volumes
There are two problem:
1. For this kind of endpoint, system-scoped token doesn't work because that
there is no project_id in the token.
2. When issue a system-scoped token, the Cinder's endpoint in the token
catalog is empty. It means the Cinder service will not be discoverable
when use system-scoped token.
** Affects: cinder
Importance: Undecided
Status: New
** Affects: keystone
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
--
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/1745905
Title:
system scope doesn't work for the service which use project specified
endpoint
Status in Cinder:
New
Status in OpenStack Identity (keystone):
New
Bug description:
For some project, such as Cinder, the endpoint is project specified, the
format is like:
http://ip/volume/v3/{project_id}/volumes
There are two problem:
1. For this kind of endpoint, system-scoped token doesn't work because that
there is no project_id in the token.
2. When issue a system-scoped token, the Cinder's endpoint in the
token catalog is empty. It means the Cinder service will not be
discoverable when use system-scoped token.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1745905/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
