Opensolr gives you three layers of protection for an index: HTTP authentication, IP-based access rules and TLS. They work individually and they work together.
01 · Enabling HTTP authentication
Open the control panel
Sign in at opensolr.com/users/login and click your index name.
Go to the Security tab
Under Manage HTTP Auth Credentials, set the username and password you want.
Save
Authentication is active immediately, on every request handler including /select and /update.
02 · Using it from your application
Send the credentials with every request. With curl:
curl -u "your-username:your-password" \ "https://YOUR_SOLR_HOST/solr/YOUR_INDEX/select?q=*:*"
Every mainstream Solr client supports HTTP basic authentication in its configuration: Solarium, SolrJ, pysolr and the rest.
03 · IP-based access rules
Per request handler
In the same Security tab, under Add new Access IP Address, you decide which addresses may reach which handler.
The default is all
Out of the box the wildcard allows every address on every handler. You narrow it where it matters.
The useful asymmetry
Restrict /update to your own servers and leave /select broader. Nobody can write to your index but your backend.
04 · TLS
Every connection across the platform, the website and all Solr cluster servers included, is encrypted. Nothing to configure: use https:// and your credentials and data are protected in transit.
05 · Practices worth keeping
Enable HTTP authentication whenever the index holds anything that is not public.
Restrict /update to your server addresses. It is the single most valuable rule.
Use credentials that are not the default, and rotate them when people leave.
Never put index credentials in client-side JavaScript. Proxy the requests through your own backend.
Want a second pair of eyes on your setup?
Send us the index name and what it is exposed to. We will tell you which of the three layers is worth adding first.