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.

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

Disambiguate s3 and gs anonymous auth #298

Open
thobrla opened this issue Sep 17, 2015 · 1 comment
Open

Disambiguate s3 and gs anonymous auth #298

thobrla opened this issue Sep 17, 2015 · 1 comment

Comments

@thobrla
Copy link
Contributor

thobrla commented Sep 17, 2015

Initially reported in this StackOverflow post.

Presently, ConfigureNoOpAuthIfNeeded is only called when no credentials are available for s3 or GCS. However, it is possible that a user may want to access one anonymously while using their credentials for the other.

We should have separate no-op auth handlers for both s3 and gs capabilities so that they can be used when necessary.

This will likely require refactoring of the auth helper logic in gslib/util.py, as we want to avoid boto.auth.get_auth_handler connecting to a service endpoint unnecessarily.

@jhoareau
Copy link

This issue is still relevant for me. Has anyone ever looked into it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants