[
https://issues.apache.org/jira/browse/SOLR-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591678#action_12591678
]
timmsc edited comment on SOLR-527 at 6/27/08 6:48 AM:
---------------------------------------------------------
I serendipitously discovered what is probably the cleanest way to only allow
commits on the slave. If the index is owned by user A with permissions
{noformat}"-rw-r--r--"{noformat} yet the slave solr process is run as user B,
only read operations are allowed. This is obvious in retrospect. I just
didn't think of it.
was (Author: timmsc):
I serendipitously discovered what is probably the cleanest way to only
allow commits on the slave. If the index is owned by user A with permissions
"-rw-r--r--" yet the slave solr process is run as user B, only read operations
are allowed. This is obvious in retrospect. I just didn't think of it.
> An XML commit only request handler
> ----------------------------------
>
> Key: SOLR-527
> URL: https://issues.apache.org/jira/browse/SOLR-527
> Project: Solr
> Issue Type: New Feature
> Components: update
> Affects Versions: 1.3
> Reporter: Sean Timm
> Priority: Trivial
> Attachments: ReadOnlyUpdateProcessorFactory.java,
> ReadOnlyUpdateProcessorFactory.java, SOLR-527.patch
>
>
> This request handler only permits <commit/> messages. It is provided as one
> way to prevent adds and deletes on a Solr slave machine that could
> potentially be accessed by outside parties where a firewall or other access
> control is either not possible or not desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
