You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Andy Throgmorton (Jira)" <ji...@apache.org> on 2020/02/12 23:45:00 UTC

[jira] [Created] (SOLR-14260) Make SchemaRegistryProvider pluggable in HttpClientUtil

Andy Throgmorton created SOLR-14260:
---------------------------------------

             Summary: 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


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.schema.registry.provider", similar to how this class allows for choosing the HttpClientBuilderFactory at runtime.

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 SchemaRegistryProvider 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org