Setting up a Keystore

Note: Any changes to the BVR, BRM, BAM and BSM keystores require BVR, BRM, BAM and BSM respectively to be restarted to take effect

BVR, BRM, BAM and BSM use Java keystore (.jks) files which are manipulated using Java's keytool command. The correct version of the keystore command to use is set by the use of the bvr_keytool symbolic link. BVR, BRM, BAM and BSM have configuration options that define the default name, location of their keystore and the alias of the key that BVR, BRM, BAM and BSM will use in the keystore. If running on the same system it will make sense for BVR, BRM, BAM and BSM to use the same keystore as they will both be providing the same certificate. This setup is fully supported by BVR, BRM, BAM and BSM.

To create a keystore, you can use the following command:: bvr_keytool -genkey -alias blueworx -keystore keystore.jks -keyalg RSA -keysize 2048 -validity NUMBER_OF_DAYS -dname "cn=SERVER_HOSTNAME"

It is important that you set the "Common Name" (CN) to the fully qualified hostname of your system (e.g. mysystem.xxxxxx.com or mysystem.xxxxxx.yyyyyyy.com). You will be asked to input a password. The default defined in both BVR, BRM, BAM and BSM configuration for this is "changeit", however it is recommended you use a more secure password than this and update the BVR, BRM, BAM and/or BSM configuration accordingly.

Note: The password of the key in the keystore must be the same as the keystore password.

For further information on the bvr_keytool command, please refer to the Oracle keytool documentation. https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html