[fix][broker] Ignore openIDTokenIssuerTrustCertsFilePath conf when blank #20745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In https://stackoverflow.com/questions/76631732/apache-pulsar-unable-to-validate-issuer-certificate-when-attempting-to-load-open, a user ran into the following stack trace:
Caused by: java.lang.IllegalArgumentException: File does not contain valid certificates:
The filename should have been included at the end of the line, but it wasn't because it was an empty string. Here is an example of what happens when you referenced a file that does not exist:
I propose we ignore "blank" inputs for the
openIDTokenIssuerTrustCertsFilePath
setting.Modifications
openIDTokenIssuerTrustCertsFilePath
is blank, do not attempt to configure a custom trust manager. Instead, use the default trust manager.Verifying this change
The risk here is very low since an empty string is invalid. The change in behavior will move from a failure at startup to using the OS's default trust store.
Documentation
doc-not-needed
Docs are not needed for this change because it makes the configuration harder to break.