BMC Remedy ARS encryption

Use this information to learn how the Java Gateway for BMC Remedy ARS interacts with the standard security encryption that is built into the BMC Remedy ARS 8.1 API.

The BMC Remedy ARS 8.1 API comes with a standard security encryption that provides a 56-bit Data Encryption Standard (DES) using Cipher Block Chaining (CBC ) mode. The algorithm uses a 512-bit RSA modulus to exchange keys and MD5 MAC to authenticate messages.

Note: You do not purchase or install the standard security encryption separately. By default, the BMC Remedy ARS 8.1 API standard security encryption is disabled. See the BMC Remedy ARS documentation for instructions on how to enable on the BMC Remedy ARS server the standard security encryption that comes with the BMC Remedy ARS 8.1 API.

BMC Remedy ARS also provides the following optional encryption products that must be purchased and installed separately from the BMC Remedy ARS 8.1 API. See the BMC Remedy ARS documentation for descriptions of these products and for instructions on how to install:

  • BMC Remedy Encryption Performance Security (BMC Remedy Encryption Performance)
  • BMC Remedy Encryption Premium Security (BMC Remedy Encryption Premium)

The following are some configuration tasks that you need to perform on both the BMC Remedy ARS server and the gateway server to configure the standard security encryption that is built into the BMC Remedy ARS 8.1 API.

Configuring the standard security encryption on the BMC Remedy ARS server

To configure the standard security encryption on the BMC Remedy ARS server, follow the steps in the BMC Remedy ARS documentation.

Configuring the standard security encryption on the gateway server

To configure the standard security encryption on the gateway server, follow these steps:

Note: The gateway requires the Bouncy Castle encryption library to communicate with the standard security encryption on the BMC Remedy ARS server. The Bouncy Castle encryption library jar file for the BMC Remedy ARS 8.1 API is called bcprov-jdk15-145.jar and it resides on the BMC Remedy ARS server. You add the Bouncy Castle encryption library jar file as an additional security provider to the Java Runtime Environment (JRE) by editing the java.security file.
  1. Copy the Bouncy Castle encryption library jar file for the BMC Remedy ARS 8.1 API, bcprov-jdk15-145.jar, from the directory on the BMC Remedy ARS server to the $JAVA_HOME/lib/jre/ext directory on the gateway server.

    Where: $JAVA_HOME specifies an environment variable that defines the path to the JRE. You must ensure that this path picks up the JRE (/lib/jre/ext) that the gateway uses.

  2. Go to the $JAVA_HOME/lib/security directory on the gateway server.
  3. Make a backup copy of the java.security file before modifying it.
  4. Open the java.security file for editing with a text editor of your choice and do the following:
    1. Locate the following property in the java.security file:
      security.provider.#=

      Where: # specifies a number (for example, 11) that identifies the security provider, in this case Bouncy Castle.

      Note: If Bouncy Castle is not listed as a security provider, you can add it by specifying a new entry after the list of existing security providers.
    2. Add the BouncyCastleProvider security provider to the property as follows (making sure to replace the value 11 with the number that identifies the Bouncy Castle security provider in your environment):
      security.provider.11=org.bouncycastle.jce.provider.BouncyCastleProvider
  5. When finished, save and close the java.security file.
    Note: If you do not correctly configure the standard security encryption on the gateway server, the gateway will fail to connect to the BMC Remedy ARS server and it will print an ERROR (9006) message in the logfile.