This documentation supports the 18.08 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Troubleshooting encryption security

This section provides basic troubleshooting information for the BMC Remedy Encryption Security products.

Java-based encryption

When you install encryption on Java-based components, the changes described in this section are made to your JRE. If you encounter problems with encryption after installing such components, verify that these changes took effect.

Java-based components include:

  • The Mid Tier
  • BMC Remedy Developer Studio
  • The Flashboards server
  • Email Engine
  • The Java plug-in server
  • User-developed clients that use the AR System Java API

Changes to be made to JRE

From your BMC Remedy Mid Tier server that is already encryption enabled, copy the following files to your JRE folder on the non-BMC Remedy machine:

  • local_policy.jar
  • US_export_policy.jar
  • java.security
    • security.provider.14=com.rsa.jsafe.provider.JsafeJCE
    • com.rsa.cryptoj.fips140initialmode=FIPS140_MODE

Note

If you want FIPS mode, use both security.provider.14=com.rsa.jsafe.provider.JsafeJCE and com.rsa.cryptoj.fips140initialmode=FIPS140_MODE. However, if you do not want FIPS mode, use only security.provider.14=com.rsa.jsafe.provider.JsafeJCE.

From the <JRE_HOME>/lib/ext/ folder, copy the following files to the <JRE_HOME>/lib/ext/ folder on the non-BMC Remedy machine:

  • cryptojce.jar
  • cryptojcommon.jar
  • jcmFIPS.jar

Warning

If you update the JRE or JDK on a computer on which Performance Security or Premium Security is installed, these modifications might be lost. To reapply them, you must reinstall Performance Security or Premium Security.


Related topics

Was this page helpful? Yes No Submitting... Thank you

Comments