tenant_id field not controlled by policy JSON file

Bug #1491466 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

The policy.json file should control the tenant_id field to authorize RW by admin and enforce no access to a tenant.

Changed in bgpvpn:
assignee: nobody → Thomas Morin (tmmorin-orange)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-bgpvpn (master)

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

commit 9a89a223829aef5a429a390def67ea1c56d86ccd
Author: Thomas Morin <email address hidden>
Date: Fri Sep 4 16:59:13 2015 +0200

    Fixes JSON policy, tenant_id control and nits

    This change updates the JSON policy file:
    - control the tenant_id resource (RW admin-only)
    - do not provide a policy for updating type (which is specified
      as a read-only attribute by the resource map)
    - some minor re-ordering for consistency

    Change-Id: Ie36b9562403eedb888e66e307a3db58cdc8c1c7c
    Closes-bug: 1491466
    Closes-bug: 1491040

Changed in bgpvpn:
status: Confirmed → Fix Committed
Changed in bgpvpn:
milestone: none → liberty
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.