[
https://issues.apache.org/jira/browse/HDDS-9671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787256#comment-17787256
]
Christos Bisias commented on HDDS-9671:
---------------------------------------
[~hemantk] you mentioned an example of mis-usage of this change. The example
was,
{quote}Let's say that a user has permissions over some keys but not every key
in the bucket. Because the user has these permissions, he also has write and
read permissions on the bucket, which would allow him to create a snapshot.
Once he creates a snapshot, then he has permissions on all the snapshot keys.
That user could be reading files that he didn't have access before and
shouldn't have access to.
{quote}
A snapshot is a representation of the filesystem's state in a certain point in
time. Keys maintain their state in the snapshot. If a user doesn't have ACL
permissions to read a key in the active filesystem, then that user won't have
permissions to read the key in the snapshot as well, regardless of whether the
user is the snapshot creator or not.
I've added a comment in the gist above to display this behavior.
Regarding use-cases, we need members of a specific team working with datasets
in a bucket, to have permission to create and delete snapshots on due course.
As displayed on the gist, these members will be able to access in the snapshot,
only the keys that they can access in the active filesystem. No more, no less.
> Users with the necessary bucket access, should be able to create snapshots
> --------------------------------------------------------------------------
>
> Key: HDDS-9671
> URL: https://issues.apache.org/jira/browse/HDDS-9671
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Christos Bisias
> Assignee: Christos Bisias
> Priority: Major
>
> Only the bucket owner and the admin have the permission to create a snapshot.
> Users with all access to a bucket should also be able to create a snapshot.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
