Versions Compared

Old Version 2

changes.mady.by.user Jonė Š.

Saved on

compared with

New Version 3

changes.mady.by.user Jonė Š.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleHow to run Teamwork Cloud in FIPS Mode?

You may encounter an error message similar to the one shown below when running Teamwork Cloud in FIPS Mode. PKCS12 keystore creation and usage are blocked in FIPS Mode for Java 11 and older versions.

Code Block
PBES2 AlgorithmParameters not available

First, make sure the initial installation was able to generate a self-signed certificate and keystore. Look for keystore.p12 and teamworkcloud.crt files in <install_root>/TeamworkCloud/configuration. If these files were not generated, run the genkey script in <install_root>/TeamworkCloud/script/linux. Check for the keystore.p12 and teamworkcloud.crt files again and change ownership to twcloud (or other username that you chose during installation.) Once these two files are generated, version 2024x should be able to run in FIPS Mode.

If the genkey script is not able to generate the self-signed certificate and keystore, set the system Java version to 17 (alternatives --config java) and try again.

For 2022x Refresh 2, append the following line to the end of the jvm.options file located in <install_root>/TeamworkCloud.

Code Block
-Dcom.redhat.fips=false

This configuration will allow Teamwork Cloud to Magic Collaboration Studio to use PKCS #12 keystore in FIPS Mode. Similar configurations will have to be set for Cassandra if encrypted communication is enabled.

...