I don't have much to add other than it is exciting to have community additions like this. The need for Solr fell off my radar but happy to see your interest, Kevin, as I've been following on the Solr lists.
Kris On Sep 27, 2016 17:18, "Larry McCay (JIRA)" <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/KNOX-528?page=com. > atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=15527579#comment-15527579 ] > > Larry McCay commented on KNOX-528: > ---------------------------------- > > [~risdenk] - thanks for the response. > > bq. Is it possible to have one service? There really isn't a difference > between the Solr UI and the APIs. It would be awesome to be able to visit a > single Knox endpoint for both. Below expands a bit more on the relationship > between the UI and the APIs and maybe that helps. > > The problem with coupling them together is that you lose the ability to > protect the REST API independently from the UI. For example, you currently > have the UI using the anonymous provider which means Knox is delegating any > authentication to the UI itself. > > If you leave the API definition in there as well then you won't be able to > expose the API independently with, say, HTTP basic auth with authentication > against LDAP. This is the most common provider use for APIs but you can > also put any number of other ones in there as well for a HTTP header based > preauthentication, etc. > > > > Support for Apache SOLR REST APIs > > --------------------------------- > > > > Key: KNOX-528 > > URL: https://issues.apache.org/jira/browse/KNOX-528 > > Project: Apache Knox > > Issue Type: Improvement > > Reporter: Rick Kellogg > > Fix For: Future > > > > > > Add Knox support for routing and securing Apache SOLR's REST APIs > > See: https://wiki.apache.org/solr/Solrj > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
