[
https://issues.apache.org/jira/browse/SOLR-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784876#comment-13784876
]
Per Steffensen commented on SOLR-4470:
--------------------------------------
We are currently upgrading our version of Solr to be 4.4.0 based instead of
4.0.0 based. Basically merging the changes between 4.0.0 and 4.4.0 into our
version of Solr. We have a lot of changes, including my solution of SOLR-4470.
After we finish the upgrade we will basically have "information" in out SVN
about how a patch on top of 4.4.0 would look. It would be a little hard to
extract because I have to filter all of our other changes from the patch, but
it can be done.
Maybe I will be able to convince my boss once again to spend time creating a
patch fitting Apache Solr, even though he kinda lost interest in that, because
patches (almost) never get into Apache Solr anyway. Will you be able to use a
4.4.0 based patch for anything?
Regarding working in small steps: It is too hard for me as a non-committer. It
will be too hard feeding in small patches, discussing forever to get it in,
then the next patch. We create a new full features (fully working and covered
by tests), because we want it, and offer it to Apache. It is not that I do not
see that argument for small patches, it is just not prioritized at our side.
> Support for basic http auth in internal solr requests
> -----------------------------------------------------
>
> Key: SOLR-4470
> URL: https://issues.apache.org/jira/browse/SOLR-4470
> Project: Solr
> Issue Type: New Feature
> Components: clients - java, multicore, replication (java), SolrCloud
> Affects Versions: 4.0
> Reporter: Per Steffensen
> Assignee: Jan Høydahl
> Labels: authentication, https, solrclient, solrcloud, ssl
> Fix For: 4.5, 5.0
>
> Attachments: SOLR-4470_branch_4x_r1452629.patch,
> SOLR-4470_branch_4x_r1452629.patch, SOLR-4470_branch_4x_r1454444.patch,
> SOLR-4470.patch, SOLR-4470.patch
>
>
> We want to protect any HTTP-resource (url). We want to require credentials no
> matter what kind of HTTP-request you make to a Solr-node.
> It can faily easy be acheived as described on
> http://wiki.apache.org/solr/SolrSecurity. This problem is that Solr-nodes
> also make "internal" request to other Solr-nodes, and for it to work
> credentials need to be provided here also.
> Ideally we would like to "forward" credentials from a particular request to
> all the "internal" sub-requests it triggers. E.g. for search and update
> request.
> But there are also "internal" requests
> * that only indirectly/asynchronously triggered from "outside" requests (e.g.
> shard creation/deletion/etc based on calls to the "Collection API")
> * that do not in any way have relation to an "outside" "super"-request (e.g.
> replica synching stuff)
> We would like to aim at a solution where "original" credentials are
> "forwarded" when a request directly/synchronously trigger a subrequest, and
> fallback to a configured "internal credentials" for the
> asynchronous/non-rooted requests.
> In our solution we would aim at only supporting basic http auth, but we would
> like to make a "framework" around it, so that not to much refactoring is
> needed if you later want to make support for other kinds of auth (e.g. digest)
> We will work at a solution but create this JIRA issue early in order to get
> input/comments from the community as early as possible.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
