GET requests on neutron API do not take into account the tenant specified in the token

[Matthieu Maquevice]

Hey,

GET requests on Neutron API (/networks, /floatingips...) return a perimeter of data with multiple tenants, even if the token used in the request specified a tenant id. Is it the normal behavior ? If so, how can we limit our scope to our tenant ?

Thanks !

[Salvatore Orlando (salvatore-orlando)]

Neutron list operations in non-admin context always return only resources owned by the tenant which submits the request (the one the token belongs to). Are you observing a tenant being able to see other tenants' resources?

Only administrators have global visibility. To scope visibility to a single tenant when submitting a list request in admin context, you can use the tenant_id query parameter (--tenant_id on the CLI).

I am not sure what "perimeter of data" refers to. I've assumed it refers to the whole list of returned data.

[Hao Wang (soccerhaotian)]

This is the same bug with 1308958. Please duplicate this one.

[Cedric Brandily (cbrandily)]

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]