Advanced Access Control Layer (AACL) #2576
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # packages/api-wcp/package.json # packages/app-page-builder/package.json # yarn.lock
|
/cypress |
|
Cypress E2E tests have been initiated (for more information, click here). ✨ |
|
/cypress |
|
Cypress E2E tests have been initiated (for more information, click here). ✨ |
|
/cypress |
|
Cypress E2E tests have been initiated (for more information, click here). ✨ |
|
/cypress |
|
Cypress E2E tests have been initiated (for more information, click here). ✨ |
|
/cypress |
|
Cypress E2E tests have been initiated (for more information, click here). ✨ |
adrians5j
added
needs-migration
project-upgrade-ready
and removed
needs-migration
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This PR integrates the new ACL-related requirements.
With this PR, open-source projects will be limited when it comes to choosing permissions in the Security Groups / API keys forms. From now, users will only be able to select No access or Full access. The only way they'll be able to choose Custom access is by linking their project with WCP and enabling the Advanced Access Control Layer (AACL) add-on.
Note: existing Webiny projects will keep working as is.
Additionally, we're introducing Teams. A new feature that enables users to assign a user to a team, which consists of one or more security groups, enabling users to be even more flexible when it comes to defining permissions for users.
Finally, groups are being renamed to roles.
How Has This Been Tested?
Jest / Cypress.
Documentation
Changelog.