Public bug reported: In light of Keystone v2.0 API removal (http://lists.openstack.org/pipermail/openstack- dev/2017-October/123783.html) in Queens.
The current in-code policy for Keystone is based on the old v2.0 policy. This is also visible by generating the sample with this command: oslopolicy-sample-generator --namespace=keystone Moving forward I believe the default in-code policy must be based on this: https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json ** Affects: keystone 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/1729800 Title: In-code policy default not suitable for v3 API Status in OpenStack Identity (keystone): New Bug description: In light of Keystone v2.0 API removal (http://lists.openstack.org/pipermail/openstack- dev/2017-October/123783.html) in Queens. The current in-code policy for Keystone is based on the old v2.0 policy. This is also visible by generating the sample with this command: oslopolicy-sample-generator --namespace=keystone Moving forward I believe the default in-code policy must be based on this: https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1729800/+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
