| 1 |
--- |
| 2 |
security: |
| 3 |
- | |
| 4 |
Fixed overly permissive default RBAC policies for several port actions |
| 5 |
that require network ownership. Those policies previously included |
| 6 |
``PROJECT_MANAGER``, which allowed any project manager to perform the |
| 7 |
action even when not owning the network (for example, on shared/RBAC |
| 8 |
networks). They now rely on ``NET_OWNER_MEMBER`` or |
| 9 |
``ADMIN_OR_NET_OWNER_MEMBER`` only. Project managers who own the |
| 10 |
network remain authorized through the default Keystone role implication |
| 11 |
chain (``manager`` implies ``member``). |
| 12 |
|
| 13 |
Affected actions: ``create_port:device_owner``, |
| 14 |
``update_port:device_owner``, ``create_port:mac_address``, |
| 15 |
``update_port:mac_address``, ``create_port:fixed_ips``, |
| 16 |
``create_port:fixed_ips:ip_address``, ``create_port:fixed_ips:subnet_id``, |
| 17 |
``update_port:fixed_ips``, ``update_port:fixed_ips:ip_address``, |
| 18 |
``update_port:fixed_ips:subnet_id``, ``create_port:port_security_enabled``, |
| 19 |
``update_port:port_security_enabled``, |
| 20 |
``create_port:allowed_address_pairs``, |
| 21 |
``create_port:allowed_address_pairs:mac_address``, |
| 22 |
``create_port:allowed_address_pairs:ip_address``, |
| 23 |
``update_port:allowed_address_pairs``, |
| 24 |
``update_port:allowed_address_pairs:mac_address``, and |
| 25 |
``update_port:allowed_address_pairs:ip_address``. |
| 26 |
upgrade: |
| 27 |
- | |
| 28 |
Default RBAC policies for the port actions listed above no longer |
| 29 |
include ``PROJECT_MANAGER``. Deployments with customized policy files |
| 30 |
should review and update those rules if they rely on the previous |
| 31 |
behaviour. |