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

Support basic HTTP authentication for remote asset API #761

Open
JSGette opened this issue Jun 27, 2024 · 1 comment
Open

Support basic HTTP authentication for remote asset API #761

JSGette opened this issue Jun 27, 2024 · 1 comment

Comments

@JSGette
Copy link

JSGette commented Jun 27, 2024

I have started bazel-remote with remote asset API enabled to use as a read-through cache for Artifactory that requires authentication. Obviously, it fails to work because I didn't set any credentials for Artifactory. It would be sufficient (in my case at least) to support basic authentication.

This is the command that I used to start bazel-remote:
./bazel-remote-2.4.4-linux-x86_64 --dir=/bazel_cache/bazel_remote --grpc_address=localhost:9092 --experimental_remote_asset_api --max_size=50

And this is the error that I get (401 obviously):
2024/06/27 11:39:32 GRPC ASSET FETCH <artifactory_url>.zip 401 Unauthorized

@malt3
Copy link

malt3 commented Mar 7, 2025

Disclaimer: not a maintainer - just another user.
I think adding support for invoking a credential helper (similar to Bazel's --credential_helper flag) would be better, so that most header-based authentication schemes can be supported.

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