[
https://issues.apache.org/jira/browse/SOLR-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-4580:
---------------------------------
Attachment: SOLR-4580_branch_4x_r1482255.patch
Patch fitting branch_4x revision 1482255. A little bit of documentation on why
the solution ended up as it did, how it works and how to use it will follow
shortly - as a comment here or on Wiki.
> Support for protecting content in ZK
> ------------------------------------
>
> Key: SOLR-4580
> URL: https://issues.apache.org/jira/browse/SOLR-4580
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.2
> Reporter: Per Steffensen
> Assignee: Per Steffensen
> Labels: security, solr, zookeeper
> Attachments: SOLR-4580_branch_4x_r1482255.patch
>
>
> We want to protect content in zookeeper.
> In order to run a CloudSolrServer in "client-space" you will have to open for
> access to zookeeper from client-space.
> If you do not trust persons or systems in client-space you want to protect
> zookeeper against evilness from client-space - e.g.
> * Changing configuration
> * Trying to mess up system by manipulating clusterstate
> * Add a delete-collection job to be carried out by the Overseer
> * etc
> Even if you do not open for zookeeper access to someone outside your "secure
> zone" you might want to protect zookeeper content from being manipulated by
> e.g.
> * Malware that found its way into secure zone
> * Other systems also using zookeeper
> * etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
