policy json rules not applied

Bug #1494771 reported by Thomas Morin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-bgpvpn
Fix Released
Critical
Thomas Morin

Bug Description

As it is, although there is a seemingly correct rule in the policy JSON file to prevent it, a random tenant still can update fields such as route-targets.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-bgpvpn (master)

Reviewed: https://review.openstack.org/222642
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=fac08cfb06779f9df6b2328e0bcca462cf452fe1
Submitter: Jenkins
Branch: master

commit fac08cfb06779f9df6b2328e0bcca462cf452fe1
Author: Thomas Morin <email address hidden>
Date: Fri Sep 11 16:33:17 2015 +0200

    Fix resource map to enforce policy

    Without enforce_policy, the policy is applied on some, but not all
    actions (eg. GET but not UPDATE).

    This change adds 'enforce_policy' to all attributes.

    Closes-Bug: 1494771
    Change-Id: Id59b5ae947d4c71ff416f26231b140554d9be1a0

Changed in bgpvpn:
status: Confirmed → Fix Committed
Changed in bgpvpn:
milestone: none → liberty
Changed in bgpvpn:
assignee: nobody → Thomas Morin (tmmorin-orange)
Changed in bgpvpn:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.