The v3 group API should account for different scopes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Colleen Murphy |
Bug Description
Keystone implemented scope_types for oslo.policy RuleDefault objects in the Queens release [0]. In order to take full advantage of scope_types, keystone is going to have to evolve policy enforcement checks in the group API. This is documented in each patch with FIXMEs [1].
System users should be able to manage groups across all domains in the deployment.
Domain users should be able to manage groups within the domain they have authorization on.
Project users shouldn't be able to manage groups at all, since group entities are domain-specific.
[0] https:/
[1] https:/
tags: | added: policy |
tags: | added: system-scope |
description: | updated |
Changed in keystone: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in keystone: | |
milestone: | none → stein-rc1 |
Changed in keystone: | |
milestone: | stein-rc1 → stein-rc2 |
Related fix proposed to branch: master /review. openstack. org/625732
Review: https:/