Many policies incorrectly have empty policy settings
Bug #1477621 reported by
Jay Bryant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Ivan Kolodyazhny |
Bug Description
In the process of addressing bug https:/
We need to go through /etc/cinder/
Changed in cinder: | |
assignee: | nobody → Ivan Kolodyazhny (e0ne) |
status: | New → In Progress |
Changed in cinder: | |
milestone: | none → liberty-rc1 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-rc1 → 7.0.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/219231 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=e065e70a69b 1b6de1bd383cb47 1dbab62b93e03a
Committed: https:/
Submitter: Jenkins
Branch: master
commit e065e70a69b1b6d e1bd383cb471dba b62b93e03a
Author: Ivan Kolodyazhny <email address hidden>
Date: Tue Sep 1 14:00:06 2015 +0300
Remove empty rules from policies for API access
Empty policy rule means that API method is allowed by anybody. Default rule
is used only if such rule is not defined in policy.json.
This patch changes empty rules to admin_api or admin_or_owner.
Closes-Bug: #1477621 b5834a21ef9fd96 7ed6e9bb695
Closes-Bug: #1491495
Change-Id: I512e65e62da7da