Apache Solr Reference Guide Covering Apache Solr 6.0

The .der files that are output from Step 2 should then be loaded to ZooKeeper under a node /keys/exe so they
are available throughout every node. You can load any number of public keys to that node and all are valid. If a
key is removed from the directory, the signatures of that key will cease to be valid. So, before removing the a
key, make sure to update your runtime library configurations with valid signatures with the update-runtimeli
b command.
At the current time, you can only use the ZooKeeper zkCli.sh (or zkCli.cmd on Windows) script to issue
these commands (the Solr version has the same name, but is not the same). If you are running the embedded
ZooKeeper that is included with Solr, you do not have this script already; in order to use it, you will need to
download a copy of ZooKeeper v3.4.6 from http://zookeeper.apache.org/. Don't worry about configuring the
download, you're just trying to get the command line utility script. When you start the script, you will connect to
the embedded ZooKeeper. If you have your own ZooKeeper ensemble running already, you can find the script
in $ZK_INSTALL/bin/zkCli.sh (or zkCli.cmd if you are using Windows).
To load the keys, you will need to connect to ZooKeeper with zkCli.sh, create the directories, and then create
the key file, as in the following example.
# Connect to ZooKeeper
# Replace the server location below with the correct ZooKeeper connect string for
your installation.
$ .bin/zkCli.sh -server localhost:9983
# After connection, you will interact with the ZK prompt.
# Create the directories
[zk: localhost:9983(CONNECTED) 5] create /keys
[zk: localhost:9983(CONNECTED) 5] create /keys/exe
# Now create the public key file in ZooKeeper
# The second path is the path to the .der file on your local machine
[zk: localhost:9983(CONNECTED) 5] create /keys/exe/pub_key.der
/myLocal/pathTo/pub_key.der
After this, any attempt to load a jar will fail. All your jars must be signed with one of your private keys for Solr to
trust it. The process to sign your jars and use the signature is outlined in Steps 4-6.
Step 4: Sign the jar File
Next you need to sign the sha1 digest of your jar file and get the base64 string.
$ openssl dgst -sha1 -sign priv_key.pem myjar.jar | openssl enc -base64
The output of this step will be a string that you will need to add the jar to your classpath in Step 6 below.
Step 5: Load the jar to the Blob Store
Load your jar to the Blob store, using the Blob Store API. This step does not require a signature; you will need
the signature in Step 6 to add it to your classpath.
curl -X POST -H 'Content-Type: application/octet-stream' --data-binary @{filename}
http://localhost:8983/solr/.system/blob/{blobname}
The blob name that you give the jar file in this step will be used as the name in the next step.
Step 6: Add the jar to the Classpath
Finally, add the jar to the classpath using the Config API as detailed above. In this step, you will need to provide
Apache Solr Reference Guide 6.0
500