[
https://issues.apache.org/jira/browse/NUTCH-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064024#comment-13064024
]
Lewis John McGibbney commented on NUTCH-987:
--------------------------------------------
Based upon the current patch you provided, I think this is a good suggestion
for inclusion. I am not currently using an auth protected Solr core in
production, but will get authentication set up in development and get this
tested Markus. It would make sense for inclusion just now as it will inevitably
become a requested feature in the future.
Further to this, to address you initial question, I agree with the comments
regarding the location to configure the auth credentials for Solr communication
as quite simply I cannot think of any other solution which would do anything
other than clutter.
> Support HTTP auth for Solr communication
> ----------------------------------------
>
> Key: NUTCH-987
> URL: https://issues.apache.org/jira/browse/NUTCH-987
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Reporter: Markus Jelsma
> Assignee: Markus Jelsma
> Fix For: 1.4, 2.0
>
> Attachments: NUTCH-987-1.3-hack.patch, NUTCH-987-1.4.1-2.patch,
> SolrUtils.java
>
>
> At the moment we cannot send data directly to a public HTTP auth protected
> Solr instance. I've a WIP that passes a configured HTTPClient object to
> CommonsHttpSolrServer, it works. This issue should add this ability to
> indexing, dedup and clean and be configured from some configuration file.
> The question is, is the current httpclient-auth.xml the correct place? It
> does provide a nice means to configure the AuthScope objects but it is used
> for fetching. But, since AuthScope is used we could easily add the
> credentials for Solr there as well and add a new nutch-default option for
> toggling HTTP auth.
> Thoughts?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
