-
Notifications
You must be signed in to change notification settings - Fork 295
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
Access restriction: Unable to add specific user per bucket #3268
Comments
What policies are you using? if the right policy is used and assigned per user, your expected behavior can be achieved |
It's not about the policies. Say if I have 2 users and 2 buckets. Say if I want user1 for bucket1 and user2 for bucket2 - In the current console, this cannot be done, you get both the users in both the buckets. |
Are you looking for something like
this allows All s3 operations on bucket specific-bucket other buckets/options are not allowed to the user whom the policy is assigned. Policies are at user/group level. You allow or deny Resources which can be one or more buckets or prefixes in a bucket. So check the policies listed under Access Audit. It means those two policies can access the bucket. Please share them to validate |
NOTE
Expected Behavior
Access isolation: Specific users can be assigned to specific buckets
Current Behavior
Any user that is added via the console is added to all the buckets. This should not be the case, each bucket should be allowed to have specific user
Possible Solution
Is there a way to allocate this via console?
Steps to Reproduce (for bugs)
Context
Regression
Your Environment
minio --version
):uname -a
):The text was updated successfully, but these errors were encountered: