-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Windows Embedded JDK is not able to use Windows certificate keystore (Windows-Root) #15305
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: feature request
Comments
foxandi
added a commit
to foxandi/bazel
that referenced
this issue
Apr 21, 2022
sgowroji
added
type: feature request
area-Windows
Windows-specific issues and feature requests
untriaged
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
labels
Apr 22, 2022
meteorcloudy
added
P2
We'll consider working on this in future. (Assignee optional)
and removed
untriaged
labels
Apr 22, 2022
foxandi
added a commit
to foxandi/bazel
that referenced
this issue
Apr 26, 2022
Fixes: bazelbuild#15305 Closes bazelbuild#15306. PiperOrigin-RevId: 443624925
ckolli5
pushed a commit
that referenced
this issue
Apr 28, 2022
I'm experiencing this issue with 6.1.0 again.
which is in detail the same as initially mentioned:
If i switch to my own jdk like
it is working well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: feature request
Description of the feature request:
Enable using the Windows host keystore for certificates instead of the keystore of the bundeled JDK.
To achieve this, the module
jdk.crypto.mscapi
needs to be added to the Windows minimal embedded JDK.This module (windows specific) is required to access the truststore of Windows. Which in term will allow to use the hosts keystore by adding
startup --host_jvm_args=-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT
.Without this module the startup option results in an exception when creating the SSLContext on bazel startup (see attached log output).
Adding the module increases the embedded JDK's size by ~38kb.
What underlying problem are you trying to solve with this feature?
Allow usage of (self-)signed or enterprise root cerrtificates (SSL) for e.g. remote-cache servers, where the sigining certificate is not part of the embedded JDK's truststore but part of the Windows hosts truststore.
Which operating system are you running Bazel on?
Windows 10
What is the output of
bazel info release
?release 5.1.1
Have you found anything relevant by searching the web?
https://groups.google.com/g/bazel-discuss/c/qeZwI_BUa8w
https://stackoverflow.com/questions/69971542/ssl-access-failure
#5741
Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: