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
I'd like to use Spring Cloud Config Client to connect to our Spring Cloud Config Server using mTLS. But after providing corresponding truststore.ks an keystore.ks in spring-cloud-config section I figured out that keystore.ks is used as a parameter for webClientOptions.setTrustStoreOptions instead of webClientOptions.setKeyStoreOptions. So no client certs could be sent to server. From my point of view current behavior looks like a bug.
Expected behavior
keystore.ks used as a parameter for webClientOptions.setKeyStoreOptions
Actual behavior
keystore.ks used as a parameter for webClientOptions.setTrustStoreOptions
How to Reproduce?
Setup Spring Cloud Config Client with truststore and keystore and try to connect Spring Cloud Config Server with mTLS enabled. No client certs will be provided.
Output of uname -a or ver
No response
Output of java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.4.2.Final
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I'd like to use Spring Cloud Config Client to connect to our Spring Cloud Config Server using mTLS. But after providing corresponding truststore.ks an keystore.ks in spring-cloud-config section I figured out that keystore.ks is used as a parameter for webClientOptions.setTrustStoreOptions instead of webClientOptions.setKeyStoreOptions. So no client certs could be sent to server. From my point of view current behavior looks like a bug.
Expected behavior
keystore.ks used as a parameter for webClientOptions.setKeyStoreOptions
Actual behavior
keystore.ks used as a parameter for webClientOptions.setTrustStoreOptions
How to Reproduce?
Setup Spring Cloud Config Client with truststore and keystore and try to connect Spring Cloud Config Server with mTLS enabled. No client certs will be provided.
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.4.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: