-
Notifications
You must be signed in to change notification settings - Fork 242
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.
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
Improvement/cldsrv-426-ACL-Implicit-Deny #5420
Improvement/cldsrv-426-ACL-Implicit-Deny #5420
Conversation
Hello benzekrimaha,My role is to assist you with the merge of this Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
ping |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command:
Alternatively, the |
/create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/8.6/improvement/CLDSRV-426-acl-impl-deny origin/development/8.6
$ git merge origin/w/7.70/improvement/CLDSRV-426-acl-impl-deny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.6/improvement/CLDSRV-426-acl-impl-deny The following options are set: create_integration_branches |
ping |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option
The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
@@ -62,11 +81,7 @@ function checkBucketAcls(bucket, requestType, canonicalID) { | |||
} | |||
} | |||
|
|||
if (requestType === 'bucketDelete' && bucket.getOwner() === canonicalID) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this PR I believe we should keep this logic for the bucketDelete API, as it seems we remove it with the changes. It may be a miss from the PoC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can also have a test for this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can actually be removed since we have this condition
if (bucket.getOwner() === canonicalID) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for the test it's already here :
description: 'should return true if bucket owner matches canonicalID', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, it was a dead code, looks good
d8b3ee4
to
1867d99
Compare
312f9d9
to
b138e9d
Compare
b138e9d
to
eecb2a9
Compare
|
||
// whitelist buckets to allow public read on objects | ||
const publicReadBuckets = process.env.ALLOW_PUBLIC_READ_BUCKETS ? | ||
process.env.ALLOW_PUBLIC_READ_BUCKETS.split(',') : []; | ||
|
||
function checkBucketAcls(bucket, requestType, canonicalID) { | ||
function checkBucketAcls(bucket, requestType, canonicalID, mainApiCall) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure where the mainApiCall
comes from and where it is set. JSDOC might be helpful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JSDOC has been added , let me know if it's still not clear enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not see it defined here:
const aclPermission = checkBucketAcls(bucket, requestType, canonicalID); |
Is it on purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it's not effecting the current behavior , it's defined on this PR ( which is aiming to update the functions calling the acl checks) : https://github.com/scality/cloudserver/pull/5432/files#diff-773344fcfc0f64145ff95eb6eccd556588c19449dc2c263a2532d4030bf00dffR360
ConflictA conflict has been raised during the update of Please resolve the conflict on the integration branch ( Here are the steps to resolve this conflict: $ git fetch
$ git checkout w/8.6/improvement/CLDSRV-426-acl-impl-deny
$ git pull # or "git reset --hard origin/w/8.6/improvement/CLDSRV-426-acl-impl-deny"
$ git merge origin/development/8.6
$ # <intense conflict resolution>
$ git commit
$ git merge origin/w/7.70/improvement/CLDSRV-426-acl-impl-deny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.6/improvement/CLDSRV-426-acl-impl-deny The following options are set: create_pull_requests, create_integration_branches |
CLDSRV-426:fixups on ACL permission checks for implicitDeny logic CLDSRV-426:better readability on ACL permission
CLDSRV-426: additionnal test for ACL permission
17d69ed
to
e0eab95
Compare
History mismatchMerge commit #fbb0de94b2d0901a610b6e26fd0351e01ac286b0 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_pull_requests, create_integration_branches |
ping |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of The following options are set: create_pull_requests, create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_pull_requests, create_integration_branches |
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve, create_pull_requests, create_integration_branches |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-426. Goodbye benzekrimaha. |
PR opened after closing : #5323
Bucket policies are not correctly interpreted, this is part of the following epic to fix that: scality/Arsenal#2181
This PR is aiming to update ACL checks for APIs with multiple permission , ticket linked to this issue here : https://scality.atlassian.net/browse/CLDSRV-426
PRs providing implicit Deny logic to CS for processing in this PR
scality/Arsenal#2181
https://github.com/scality/Vault/pull/2135
#5322
Tests have also been added.
I'm not bumping a new CLDSRV version since a new version has been created in this merged PR : #5322 , Please let me know if it needs to be done anyways.