-
Notifications
You must be signed in to change notification settings - Fork 160
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
grpc authentication using htpasswd #575
Comments
Hi, could you copy+paste the exact error message you get on the bazel side? And any relevant logs from bazel-remote when this happens. |
Hi, so when i pass any command with bazel i get the same response when its passed with userid and pwd, eg bazel clean ERROR: Failed to query remote execution capabilities: UNIMPLEMENTED: HTTP status code 404 So its like whenever any additional parameter passed along with the url in case of grpc, it throws this error. |
The .bazelci/basic-auth-tests.sh script that's run in CI does I'm not sure what the key/value are in your question.
I wonder if the line above means that the load balancer is returning an error, without reaching bazel-remote? Do you get any logs on the bazel-remote side when trying this? |
The only logs i could see is 2022/09/06 11:28:55 GET 400 172.24.211.176 / Yes it just says that my LB doesnt have such url and rejecting the request. Do i need to have nginx ingress as well along with my ALB? |
Those bazel-remote logs are from bazel-remote's http server/port, for which |
It was related to my htpasswd issue and once changed it, i dont see any 400 error and i could see bazel logs in my console. And also it doesnt throw me an error when i pass grpcs://user:pwd@host:port --remote-header... But i see this error in my bazel build as So my auth credentials arent working. Do i need to create a secret\something? I have it as part of my s3 folder. |
What are your bazel and bazel-remote command lines? |
From what I see, it is not supported by Bazel — gRPC over SSL doesn't support basic auth using URL. Please see bazelbuild/bazel#13378 (comment) and buildfarm/buildfarm#756 (comment) Looks like, the only way to specify credentials in |
Hi
Its not an issue, may be im missing something. I'm setting up the cache in EKS with an ALB and using grpcs for the remote cache. I wanted to use htpasswd based authentication for authenticating. The authentication works well when used https instead of grpcs but with grpcs i get an error as unimplemented code. Is there any specific configuration for grpcs needs to be done?
without auth, it works fine and i could upload to the s3 bucket the cache files.
Im using build --remote_cache=grpcs://user:pwd@host:9092 --remote_header=key=value.
Also I would like to know is it possible to pass directly as grpcs://user:pwd@host:9092/value instead of using a remote_header?
The text was updated successfully, but these errors were encountered: