spring-cloud / spring-cloud/spring-cloud-config

Add RestTemplateCustomizer to ConfigServicePropertySourceLocator

Open
#1,563 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
2k
Forks
1.3k
Avg merge
2d 59m
Merged PRs (30d)
16

Description

On the current project we use spring cloud config solution. The problem is that the config-server was deployed behind https load-balancer and we got the follfowing issues:

c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for "****": java.security.cert.CertificateException: No subject alternative DNS name matching *** found.; nested exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching ***

According documentation we have solved that by custom ConfigServicePropertySourceLocator and RestTemplate configuration used there, but that was really tricky, we spend a few hours to find the proper client configuration.

The solution we'd like to have is just an opportunity to change RestTempalte config used in ConfigServicePropertySourceLocator via application.properties. In our case that could be something like spring.cloud.config.clinet.ssl.enalbed=false

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at ConfigServicePropertySourceLocator and trace the RestTemplate configuration used for config-server requests. Check how application.properties can supply the requested client setting; done when that configuration can be changed without a custom locator or RestTemplate implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.