To change Solr's default port number just pass -Djetty.port=xxxx on the command line, works a treat.
As Solr is deployed as a web-app, it is assumed that the administrator would be familiar with web apps, servlet containers and their security, if not, then that is something you need to investigate generally. Solr comes out of the box with Jetty, but lots of installations use Tomcat and other Servlet Engines, so having standard procedures isn't really viable when all the servlet containers use different mechanisms to configure their security. I believe historically that out of the box deployment was very much an example installation (just for testing/getting to know Solr), and not recommended as a baseline for building a production system, that said, I know there is work on-going to make it a lot more user-friendly. I can't say I've done it but http://www.eclipse.org/jetty/documentation/current/configuring-security.html#configuring-security-authentication seems a reasonable place to start with the default embedded Jetty installation that Solr uses. I would suggest starting with a simpler webapp and learning the basic of web app deployment and security through Jetty (or Tomcat, or whatever you want to use). web.xml is a standard file in servlet engines, in our installation it is in <solr-home>solr-webapp/webapp/WEB-INF/web.xml. It is contained within solr.war, and is deployed as part of the first time you run Solr, so if you want to change it, you can run solr once, and then hack that file, but to do it properly, you will need to re-bundle it back into solr.war. On 24 June 2013 08:04, K Wong <wongo...@gmail.com> wrote: > You might want to read up on Jetty webserver security if that is what you > are using for the web container. > > K >
