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

Remove "Allow List All Bucket Names" scope from S3 and document required scopes #339

Open
SailReal opened this issue Jul 16, 2021 · 2 comments · May be fixed by #509
Open

Remove "Allow List All Bucket Names" scope from S3 and document required scopes #339

SailReal opened this issue Jul 16, 2021 · 2 comments · May be fixed by #509
Labels
good first issue Issues easy to implement or with a narrow scope of changes storage:s3 type:feature-request New feature or request
Milestone
Backlog

Comments

@SailReal
Copy link
Member

Summary

As discussed in #338, drop "Allow List All Bucket Names" and do an object listing during authentication on the provided bucket and see if there is a NO_SUCH_BUCKET error.

Document all remaining scopes.

Motivation

As a user I want to grant the provided access keys as less scopes as possible as well as know which scopes are requried.
@SailReal SailReal added type:feature-request New feature or request storage:s3 labels Jul 16, 2021
@SailReal SailReal added the good first issue Issues easy to implement or with a narrow scope of changes label Oct 4, 2021
@stale

This comment was marked as outdated.

Sign in to view
@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Apr 18, 2022
@SailReal SailReal added this to the Backlog milestone Apr 19, 2022
@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Apr 19, 2022
@JaniruTEC JaniruTEC linked a pull request Nov 8, 2023 that will close this issue
Draft
@SailReal SailReal mentioned this issue Nov 25, 2024
Closed
@s-h-a-d-o-w
Copy link

Leaving a reminder here that once this is implemented, the note in the docs about this has to be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Issues easy to implement or with a narrow scope of changes storage:s3 type:feature-request New feature or request
Projects
None yet
Milestone
Backlog
Development

Successfully merging a pull request may close this issue.

Remove unnecessary scopes and document required scopes cryptomator/android
2 participants
@SailReal @s-h-a-d-o-w