(Optional) Configure JDK to Use the Unlimited Strength Java Cryptography Jars
PPM supports control over the encryption suites used by its SSL (TLS) sockets. This can be specified by the server configuration parameter
The value for this parameter should contain a comma-separated list of the encryption suites to be made available to PPM Centre. These should be specified using the standard SSL/TLS cipher suite names.
For example, to specify that PPM should only establish connections using the TLS_DHE_RSA_WITH_AES_256_CBC_SHA cipher suite:
If using AES256 or similarly strong encryption, the JDK used by both PPM and the client must be configured to use the unlimited strength Java cryptography jars, if this is permissible in your jurisdiction and under US export laws.
SSL_ENCRYPTION_SUITES parameter only impacts the encryption algorithm used for RMIS traffic. There is no impact on HTTPS (SSL) encryption, nor on how the passwords and sensitive data are encrypted in PPM.
To configure your JDK to use the unlimited strength Java cryptography jars,
Scroll down to the end of the page and download the unlimited strength Java cryptography jars that match your JDK version.
For JDK 1.7.0, download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7 (
Extract the downloaded zip package.
US_export_policy.jarfiles to the
<JDK_HOME>/jre/lib/securitydirectory on both your server side and client side to replace the existing files.
Note: If you enabled secure RMI and are using a high strength encryption suite, such as AES256, make sure to follow the steps above to install the unlimited jars on machines which will run workbench.