spring-projects / spring-projects/spring-boot
Provide information about the source of the trust material in SslBundle's toString()
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Hi,
we are using different bundles and the one who does configure them and the one who does operate the app in question are not always the same person.
We're logging the used bundle, however we only get this as toString():
[org.springframework.boot.autoconfigure.ssl.PropertiesSslBundle@166e52ca]
Tomcat e.g. does print something like this for the connector config:
Connector [https-openssl-nio-8443], TLS virtual host [_default_], certificate type [UNDEFINED] configured from keystore [/home/app/.keystore] using alias [tomcat] with trust store [null]
It would be nice if a better toString could be done which prints all important configured props of the bundle (without sensitive stuff like passwords etc.), but ciphers, options, aliases, key / trust store path etc. would be nice to have on the configured bundle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating SslBundle and the PropertiesSslBundle implementation, then inspect how the bundle currently represents its configuration and whether related tests cover toString(). Done means the string identifies useful non-sensitive trust and key material sources and configuration details without exposing passwords or other secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100