Describe the bug
In spring-cloud SR8, we can enable client side tls by setting eureka.client.tls.keystoretype, eureka.client.tls.keystore, eureka.client.tls.enabled. But it cannot work in 2020.0.0-m5.
After some investigation I found Spring cloud 2020.0.0-m5 removes jersey client with this change. Then DiscoveryClient will use RestTemplate, while the RestTemplateTransportClientFactories does not accept sslContext. And in SR8, DiscoveryClient will use JerseyClient, JersyClient can work with client tls perfectly.
I know I can mitigate this issue by adding jersey dependency in my project, but I am still wonder if it is a bug in RestTemplate
Comment From: spencergibb
If you include the Jersey client dependencies it will work again
Comment From: zmssp
Yes, I know, I can mitigate it by add Jersy client. I still wonder is it a bug in RestTemplate?
To us, we wish our customer can use Azure Spring Cloud without code any change.
So we do have a plan to support client tls in RestTemplate?