-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
javax.net.ssl
TLS configuration does not work in native mode
#46368
Labels
Milestone
Comments
/cc @radcortez (config) |
cc @cescoffier |
ppalaga
added a commit
to ppalaga/quarkus
that referenced
this issue
Feb 19, 2025
ppalaga
added a commit
to ppalaga/quarkus
that referenced
this issue
Feb 19, 2025
Here is the idea: #46379 |
ppalaga
added a commit
to ppalaga/quarkus
that referenced
this issue
Feb 20, 2025
Oh right... that's a great catch. |
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Feb 24, 2025
…rkusio#46368 (cherry picked from commit ababb2f)
ppalaga
added a commit
to ppalaga/quarkus-cxf
that referenced
this issue
Feb 25, 2025
ppalaga
added a commit
to quarkiverse/quarkus-cxf
that referenced
this issue
Feb 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
javax.net.ssl
as a built-in named TLS configuration was introduced recently. While it works as expected in JVM mode, it does not work in native mode. This is because the lookup of the defaultcacerts
trust store file relies onjava.home
system property, which is not set at native image runtime. There is no home directory of JRE for native executables and therefore there is also nocacerts
file.When
javax.net.ssl
is used in native mode, the following exception is thrown:Related information
GraalVM seems not not to be embedding the
cacerts
in the native executables by design - https://www.graalvm.org/latest/reference-manual/native-image/dynamic-features/CertificateManagement/Here is what it does:
Possible solution
There seems to be a programmatic way to access the certs from the default trust store via
I'd try to make
io.quarkus.tls.runtime.CertificateRecorder
use those certs forjavax.net.ssl
unless somebody has a better idea?The text was updated successfully, but these errors were encountered: