You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User may want to use the default Java truststore that is usually available under $JAVA_HOME/lib/security/jssecacerts, $JAVA_HOME/lib/security/cacerts or overridden throw javax.net.ssl.trustStore system property.
To make this use case easier, we should introduce a reserved javax.net.ssl TLS configuration name with the following properties:
Users can use javax.net.ssl as a value for various *.tls-configuration-name options, such as quarkus.http.tls-configuration-name
Users do not need to define that named TLS config by themselves
A TLS configuration with name javax.net.ssl would be created on demand by the TLS registry extension
The text was updated successfully, but these errors were encountered:
ppalaga
changed the title
[TLS Registry] TLS configuration javax.net.ssl created on demand from javax.net.ssl.* system properties
[TLS Registry] provide a TLS configuration called javax.net.ssl having truststore set in the same way as default SunJSSE provider
Dec 18, 2024
ppalaga
changed the title
[TLS Registry] provide a TLS configuration called javax.net.ssl having truststore set in the same way as default SunJSSE provider
TLS Registry: provide a TLS configuration called javax.net.ssl having truststore set in the same way as default SunJSSE provider
Dec 18, 2024
Description
User may want to use the default Java truststore that is usually available under
$JAVA_HOME/lib/security/jssecacerts
,$JAVA_HOME/lib/security/cacerts
or overridden throwjavax.net.ssl.trustStore
system property.To make this use case easier, we should introduce a reserved
javax.net.ssl
TLS configuration name with the following properties:javax.net.ssl
as a value for various*.tls-configuration-name
options, such asquarkus.http.tls-configuration-name
javax.net.ssl
would be created on demand by the TLS registry extensionThe text was updated successfully, but these errors were encountered: