oslopolicy-checker hardcodes match of project_id
Bug #1795496 reported by
Adam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.policy |
Confirmed
|
Medium
|
Harry Rybacki |
Bug Description
One shortcut I made when writing the policy checker was that I ensured the project ID from the token would be used in the target:
access_data = jsonutils.
access_
...
target = {"project_id": access_
This implies to a user that the API is actually checking the scope of the target. However, there is no way to pass target data in to the the policy engine.
Thus, there is no way to confirm that it will reject if the target has a different project_id, nor does it allow more complex checks on other attributes from the target data.
Changed in oslo.policy: | |
assignee: | nobody → Harry Rybacki (hrybacki-h) |
Changed in oslo.policy: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.