RANGER-4776: SolrAuditDestination uses local SSLContext instead of se… #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tting the system-wide default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…tting the system-wide default
What changes were proposed in this pull request?
In order to avoid setting the system-wide
SSLContextinSolrAuditDestination(which may affect other components running in the same JVM negatively), use Solr'sHttpClientUtil.setSocketFactoryRegistryProvider()to pass theSSLContextto the Solr client locally.How was this patch tested?
We use the Ranger Plugin in Apache NiFi.
Before the change, Azure components in NiFi failed with "unable to find valid certification path to requested target" error.
After the change, the Ranger - Solr connection still works and the Azure components can also access the needed certificate in the system default truststore (cacerts).