[
https://issues.apache.org/jira/browse/SOLR-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-14260.
---------------------------------
Resolution: Fixed
Thanks for contributing Andy!
> Make SchemaRegistryProvider pluggable in HttpClientUtil
> -------------------------------------------------------
>
> Key: SOLR-14260
> URL: https://issues.apache.org/jira/browse/SOLR-14260
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Andy Throgmorton
> Assignee: David Smiley
> Priority: Minor
> Fix For: 8.6
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> HttpClientUtil.java defines and uses an abstract SchemaRegistryProvider for
> mapping a protocol to an Apache ConnectionSocketFactory. There is only one
> implementation of this abstract class (outside of test cases). Currently, it
> is not override-able at runtime.
> This PR adds the ability to override the registry provider at runtime, using
> the class name value provided by
> "solr.httpclient.socketFactory.registry.provider", similar to how this class
> allows for choosing the HttpClientBuilderFactory at runtime. And
> SchemaRegistryProvider is renamed to SocketFactoryRegistryProvider.
> We've implemented a custom mTLS solution in Solr (which uses a custom SSL
> context). This change helps us more easily configure Solr in a modular way,
> since we've implemented a custom SocketFactoryRegistryProvider that
> configures Apache clients to use our SSL context.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
