You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Peter Sturge (JIRA)" <ji...@apache.org> on 2012/04/28 13:55:48 UTC

[jira] [Commented] (SOLR-3421) Distributed Search doesn't allow for HTTP Authentication

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

Peter Sturge commented on SOLR-3421:
------------------------------------

There is an existing patch for this behaviour - see:
    issues.apache.org/jira/browse/SOLR-1861

This patch allows distributed credentials to be passed inside the url, where SearchHandler then parses this an creates HttpConnections for each shard in the distributed search.
Some useful extensions to this approach would be the use of certificates (instead of explicit credentials), and/or acl lists stored on the server side, with pre-authentication (e.g. via passing hash values instead of explicit credentials). The base mechanism provided in this patch can be used in both cases.

HTH!
Peter

                
> Distributed Search doesn't allow for HTTP Authentication
> --------------------------------------------------------
>
>                 Key: SOLR-3421
>                 URL: https://issues.apache.org/jira/browse/SOLR-3421
>             Project: Solr
>          Issue Type: New Feature
>          Components: SearchComponents - other
>    Affects Versions: 3.6, 4.0
>         Environment: Sharded solr cluster
>            Reporter: Michael Della Bitta
>            Priority: Minor
>              Labels: auth, distributed_search, ssl
>
> The distributed search feature allows one to configure the list of shards the SearchHandler should query and aggregate results from using the "shards" parameter. Unfortunately, there is no way to configure any sort of authentication between shards and a distributed search-enabled SearchHandler. It'd be good to be able to specify an authentication type, auth credentials, and transport security to allow installations that don't have the benefit of being protected by a firewall some measure of security.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org