/auth/domains does not necessarily return a distinct list

Bug #1386264 reported by Henry Nash
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Medium
David Stanek

Bug Description

The underlying code list_domains_for_user() does not (unlike the project equivalent) attempt to filter out duplicates (which would happen if a user had, say, a direct role and a group role, or multiple inherited roles). In all our APIs that return entities based on their effective assignments, we try and make sure we return a distinct list.

Revision history for this message
Henry Nash (henry-nash) wrote :

This is one in a series of defects I found by code inspection while producing a WIP code example for https://review.openstack.org/#/c/129397/. See for the WIP code: https://review.openstack.org/#/c/130954/

Changed in keystone:
importance: Undecided → Medium
assignee: nobody → Henry Nash (henry-nash)
Changed in keystone:
status: New → Triaged
Revision history for this message
Steve Martinelli (stevemar) wrote :

unassigning due to inactivity

Changed in keystone:
assignee: Henry Nash (henry-nash) → nobody
Revision history for this message
Steve Martinelli (stevemar) wrote :

With the migration to using role assignments, I believe this is no longer valid?

Revision history for this message
David Stanek (dstanek) wrote :
Changed in keystone:
assignee: nobody → David Stanek (dstanek)
Revision history for this message
Henry Nash (henry-nash) wrote :

Yep, I agree - that did fix this issue. I'll mark it as fixed.

Changed in keystone:
status: Triaged → Fix Committed
Revision history for this message
Steve Martinelli (stevemar) wrote :

marking as released

Changed in keystone:
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.