keystone middleware doesn't respect reseller prefix

Bug #1558216 reported by John Dickinson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Confirmed
Medium
Unassigned

Bug Description

The keystone middleware in the Swift repo doesn't filter requests based on the configured reseller prefix. This results in two problems:

1) The keystone middleware must be placed before all other auth middleware in the pipeline or it will overwrite other settings (ie it doesn't play well with others). A side-effect is that you cannot have more than one keystone configured and installed

2) Every request, regardless of reseller prefix, results in a request to keystone, thus causing unnecessary load on systems.

Nandini (nandini-tata)
Changed in swift:
assignee: nobody → Nandini (nandini-tata)
Robin Naundorf (senk)
Changed in swift:
status: New → In Progress
Revision history for this message
Nandini (nandini-tata) wrote :

Hello Robin,

Checking in to see if you started working on this bug.

Revision history for this message
Tim Burke (1-tim-z) wrote :

There haven't been any updates on the bug, and I haven't seen any patches in Gerrit -- moving this out of in-progress.

Changed in swift:
status: In Progress → Confirmed
assignee: Nandini (nandini-tata) → nobody
Revision history for this message
Tim Burke (1-tim-z) wrote :

Oh, hey, https://review.opendev.org/#/c/593977/ seems like it'd fix this!

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.