lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joel Bernstein <>
Subject Re: Solr M2M authentication on Jetty
Date Wed, 18 May 2016 20:59:21 GMT

You may want to investigate the Streaming Expression functions in Solr 6.0.
There are some interesting functions that might help with some of the tasks
you mentioned:

1) topic: let's users subscribe to a query and returns all new documents
for a query.
2) daemon: allows you to setup processes in Solr that push data to users.
This would eliminate the need for users to have direct access to Solr if
the authentication issues become a problem. Currently the only way to push
data is to use the update function which pushes data to another Solr
collection. But it would be easy to write a stream that pushed data to
splunk, or another type of system.

Joel Bernstein

On Wed, May 18, 2016 at 2:02 PM, Gregoric, James <> wrote:

> Correction:  Item 1 is not an absolute requirement; we can use Apache or
> Tomcat if that makes things any easier.
> -----Original Message-----
> From: Gregoric, James []
> Sent: Wednesday, May 18, 2016 1:54 PM
> To:
> Subject: Solr M2M authentication on Jetty
> Dear Solr Community,
> We would like to provide an in-house group of users access to our Solr
> database in a way that meets the following specifications:
> 1.       Use the Jetty web service that Solr 6.0 installs by default.
> 2.       Provide an M2M (machine-to-machine) interface, so a user can
> setup a cron job that periodically executes a query and stores the results.
> 3.       Authentication credentials for the M2M interface to the Jetty
> service are provided by an LDAP service so it is possible to log who is
> accessing what data.
> 4.       Result data retrieved from Solr (result UIDs) are recorded by
> Can you offer advice and/or point us to a working example of any of these
> specification items?
> Here's what we have so far:
> A.      Completed item 1 above.  We've installed Solr 6.0 with Jetty on a
> Linux VM and it works great.
> B.      Partially addressed item 3 above in that we can login to Jetty
> using LDAP.  However, our implementation is such that the login credentials
> are input interactively (via a login dialog).  We don't yet know how to
> perform this login from machine to machine.  This is the main sticking
> point right now.
> Any insight you might provide would be greatly appreciated.
> Regards,
> Jim Gregoric
> Boston Children's Hospital, Clinical Research Informatics

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message