Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tenant separation within SCS #188

Open
14 tasks
fkr opened this issue Oct 12, 2022 · 0 comments
Open
14 tasks

Tenant separation within SCS #188

fkr opened this issue Oct 12, 2022 · 0 comments
Labels
epic Issues that are spread across multiple sprints IAM Issues or pull requests relevant for SIG IAM SCS is federated SCS is federated

Comments

@fkr
Copy link
Member

fkr commented Oct 12, 2022 •
edited
Loading

As a SCS Customer I want to have confidentiality and integrity of the resources I have configured in my domain.

Definition of Ready:

  • User Story is small enough to be finished within one sprint
  • User Story is clear and understood by the whole team
  • Acceptance criteria are defined
  • Acceptance criteria are clear and understood by the whole team

Definition of Done:

  • User Stories for extending keystone to support a manager role need to be written #206
  • Architecture is properly documented and can easily be reviewed by external parties
  • It is automatically tested that separation of users, projects and domains is secure even in a federated scenario
  • As a SCS Operator I'm able to restrict the customer/tenant admin from Elevation of Privilege (leaving the scope of their domain) by creating new admin account outside of his scope
  • Tenant separation is default, so that tenants are not aware of each other
  • All acceptance criteria are met
  • Changes have been reviewed
  • CI tests have run successfully
  • Documentation has been updated
  • Release Notes have been updated
@fkr fkr added epic Issues that are spread across multiple sprints IAM Issues or pull requests relevant for SIG IAM needs refinement User stories that need to be refined for further progress SCS is federated SCS is federated labels Oct 12, 2022
@fkr fkr removed the needs refinement User stories that need to be refined for further progress label Jan 25, 2023
@tibeer tibeer mentioned this issue Mar 29, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic Issues that are spread across multiple sprints IAM Issues or pull requests relevant for SIG IAM SCS is federated SCS is federated
Projects
Sovereign Cloud Stack
Status: Refined Stories
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fkr