[ 
https://issues.apache.org/jira/browse/SOLR-13502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842199#comment-17842199
 ] 

John Durham commented on SOLR-13502:
------------------------------------

I think having it be in addition to 4lw makes sense. I'll work towards making 
it work with either the original 4lw or admin server.

So far I'm not seeing SSL supported on admin server. However, with admin server 
being served on a separate port (8080 default) from the regular client 
connections (port 2181), at least some kind of monitoring/metrics will be 
available even if SSL isn't currently available.

> Investigate using something other than ZooKeeper's "4 letter words" for the 
> admin UI status
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13502
>                 URL: https://issues.apache.org/jira/browse/SOLR-13502
>             Project: Solr
>          Issue Type: Improvement
>          Components: Admin UI
>            Reporter: Erick Erickson
>            Priority: Major
>
> ZooKeeper 3.5.5 requires a whitelist of allowed "4 letter words". The only 
> place I see on a quick look at the Solr code where 4lws are used is in the 
> admin UI "ZK Status" link.
> In order to use the admin UI "ZK Status" link, users will have to modify 
> their zoo.cfg file with
> {code}
> 4lw.commands.whitelist=mntr,conf,ruok
> {code}
> This JIRA is to see if there are alternatives to using 4lw for the admin UI.
> This depends on SOLR-8346. If we find an alternative, we need to remove the 
> additions to the ref guide that mention changing zoo.cfg (just scan for 4lw 
> in all the .adoc files) and remove SolrZkServer.ZK_WHITELIST_PROPERTY and all 
> references to it (SolrZkServer and SolrTestCaseJ4).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to