Skip to content

Commit 369c698

Browse files
Remove outdated limitation not applicable to 2024.1
Signed-off-by: Markus Hentsch <[email protected]>
1 parent 14e80c0 commit 369c698

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

Standards/scs-0302-v1-domain-manager-role.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -89,16 +89,12 @@ This means that by creating a new role and extending Keystone's API policy confi
8989

9090
### Limitations
9191

92-
The approach described in this standard imposes the following limitations:
92+
The approach described in this standard imposes the following limitation:
9393

94-
1. as a result of the "`identity:list_domains`" rule (see below), Domain Managers are able to see all domains[^5] via "`openstack domain list`" and can inspect the metadata of other domains with "`openstack domain show`"
95-
2. as a result of the "`identity:list_roles`" rule (see below), Domain Managers are able to see all roles via "`openstack role list`" and can inspect the metadata of other roles with "`openstack role show`"
94+
As a result of the "`identity:list_roles`" rule (see below), Domain Managers are able to see all roles via "`openstack role list`" and can inspect the metadata of any role with "`openstack role show`"
9695

97-
**As a result of points 1 and 2, metadata of all domains and roles will be exposed to all Domain Managers!**
96+
If this limitation poses a concern for a CSP, they may abstain from granting the `"manager"` role to any user in a domain scope, effectively disabling the Domain Manager functionality. See [Impact](#impact).
9897

99-
If a CSP deems either of these points critical, they may abstain from granting the `"manager"` role to any user in a domain scope, effectively disabling the Domain Manager functionality. See [Impact](#impact).
100-
101-
[^5]: see the [corresponding Launchpad bug at Keystone](https://bugs.launchpad.net/keystone/+bug/2041611)
10298

10399
## Decision
104100

@@ -231,9 +227,9 @@ They are used as a basis for the domain-manager-specific changes which are imple
231227
The section of "`base_*`" rules is meant for easy maintenance/update of default rules while keeping the domain-manager-specific rules separate.
232228

233229
> **Note:**
234-
> The "`or rule:admin_required`" appendix to the rule definitions in "Section B" is included for backwards compatibility with environments not yet fully configured for the new secure RBAC standard[^6].
230+
> The "`or rule:admin_required`" appendix to the rule definitions in "Section B" is included for backwards compatibility with environments not yet fully configured for the new secure RBAC standard[^5].
235231

236-
[^6]: [OpenStack Technical Committee Governance Documents: Consistent and Secure Default RBAC](https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html)
232+
[^5]: [OpenStack Technical Committee Governance Documents: Consistent and Secure Default RBAC](https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html)
237233

238234
#### Specifying manageable roles via "`is_domain_managed_role`"
239235

0 commit comments

Comments
 (0)