| commit | aaf65b97b7cd75160b4b4dcc9149fb9fc60e1759 | [log] [tgz] |
|---|---|---|
| author | Kevin Lin <developer@kevinlin.info> | Tue Dec 14 11:37:58 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 14 11:39:21 2021 -0800 |
| tree | a3ffc5cf1de6c7705f4b7eb8b7d4a4e6fe2440fe | |
| parent | 7074bcff7d1fcba7230fec11ce1d155b6e3d51b1 [diff] |
Remote: Support client TLS authentication for remote caches over HTTP Fixes #14397. This change augments the `SslContext` created for TLS HTTP remote caches to include the client certificate, client key, and optional root CA as specified on the command line with `--tls_client_certificate`, `--tls_client_key`, and `--tls_certificate`, respectively. The implementation proposes propagating `AuthAndTLSOptions` through `RemoteCacheClientFactory` and `HttpCacheClient` in order to expose the relevant file paths to the logic that creates the SSL context for use by the HTTP remote cache client. Closes #14398. PiperOrigin-RevId: 416354592
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
