Re: BYOPW in security.json

2016-04-08 Thread Jan Høydahl
t;admin", to make the CLI more usable. > > -Original Message- > From: Jan Høydahl [mailto:jan@cominvent.com] > Sent: Wednesday, April 06, 2016 4:18 AM > To: solr-user@lucene.apache.org > Subject: Re: BYOPW in security.json > > Hi > > Note that storing the use

RE: BYOPW in security.json

2016-04-06 Thread Davis, Daniel (NIH/NLM) [C]
f IPs that are assumed to be "admin", to make the CLI more usable. -Original Message- From: Jan Høydahl [mailto:jan@cominvent.com] Sent: Wednesday, April 06, 2016 4:18 AM To: solr-user@lucene.apache.org Subject: Re: BYOPW in security.json Hi Note that storing the user name

RE: BYOPW in security.json

2016-04-06 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
Thanks. I googled to look for examples of how to proceed, and notice that you opened SOLR-8951 Thanks again -Original Message- From: Jan Høydahl [mailto:jan@cominvent.com] Sent: Wednesday, April 06, 2016 4:18 AM To: solr-user@lucene.apache.org Subject: Re: BYOPW in security.json

Re: BYOPW in security.json

2016-04-06 Thread Jan Høydahl
Hi Note that storing the user names and passwords in security.json is just one implementation, to easily get started. It uses the Sha256AuthenticationProvider class, which is pluggable. That means that if you require Basic Auth with some form of self-service management, you could/should add ano