[
https://issues.apache.org/jira/browse/SOLR-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795147#comment-17795147
]
David Smiley commented on SOLR-16743:
-------------------------------------
BATs tests have been failing:
[https://ge.apache.org/s/vsuyglwmmrgba/console-log?page=2#L1263]
BTW interesting to see this feature. I've witnessed this approach
conceptually, albeit with homegrown keystores (and thus can be more Java
generic instead of Jetty specific). Managing it across an enterprise is a
headache though; too many nuances for each service to comply with. Istio/Mesh
is a far simpler integration.
> Auto reload keystore/truststore on change
> -----------------------------------------
>
> Key: SOLR-16743
> URL: https://issues.apache.org/jira/browse/SOLR-16743
> Project: Solr
> Issue Type: Improvement
> Components: Server, SolrJ
> Reporter: Houston Putman
> Assignee: Tomas Eduardo Fernandez Lobbe
> Priority: Major
> Fix For: main (10.0), 9.5
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently everyone who uses Solr with SSL must restart their clusters when
> new certificates are created.
> Jetty comes with an
> [ssl-reload|https://www.eclipse.org/jetty/documentation/jetty-10/operations-guide/index.html#og-module-ssl-reload]
> module for reloading the server's keystore.
> For the client we would likely need to reload the truststore, but that
> requires more investigation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
