You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
garloff opened this issue
Feb 14, 2023
· 2 comments
Assignees
Labels
IaaSIssues or pull requests relevant for Team1: IaaSIAMIssues or pull requests relevant for SIG IAMSCS-VP10Related to tender lot SCS-VP10standardsIssues / ADR / pull requests relevant for standardization & certificationupstreamImplemented directly in the upstream
Decisions that led to the current Domain Manager standard draft, its limitations and specifics need to be documented as a Decision Record in the standards repository.
The text was updated successfully, but these errors were encountered:
garloff
added
upstream
Implemented directly in the upstream
IAM
Issues or pull requests relevant for SIG IAM
standards
Issues / ADR / pull requests relevant for standardization & certification
labels
Feb 14, 2023
As a SCS Customer I have rights to manage my resources to define roles and map them to access privileges.
in the issue description for removal because it is technically impossible to achieve this.
Defining roles (along with access privileges) is only possible via each OpenStack service's policy.yaml configuration file. The RBAC privilege mappings of APIs (as per oslo.policy's policy.yaml) are not exposed via APIs and thus cannot be modified by customers. Creating and assigning roles via Keystone API has no effect unless a matching role mapping is properly included in the oslo.policy files.
As agreed upon with @fkr the decision record history was integrated into the standard document itself as an appendix. It was merged together with the draft in #343.
IaaSIssues or pull requests relevant for Team1: IaaSIAMIssues or pull requests relevant for SIG IAMSCS-VP10Related to tender lot SCS-VP10standardsIssues / ADR / pull requests relevant for standardization & certificationupstreamImplemented directly in the upstream
Decisions that led to the current Domain Manager standard draft, its limitations and specifics need to be documented as a Decision Record in the standards repository.
The text was updated successfully, but these errors were encountered: