Page History

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.

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>/MagicCollaborationStudio/TeamworkCloud/configuration. If these files were not generated, run the genkey script in <install_root>/MagicCollaborationStudio/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>/MagicCollaborationStudio/TeamworkCloud.

-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.

It is possible to install Teamwork Cloud Magic Collaboration Studio without internet access, provided that the prerequisite packages are available locally. Access to a locally-managed repository server is a recommended for offline installation. Linux packages often have dependencies that are pulled and installed automatically when connecting to a repository. Manual download of Linux packages may require a trial-and-error process of retrieving dependencies.

Access to repository server

If you have access to a locally-managed repository server, go through the installation sections and download all prerequisite packages listed. Edit the installation scripts and replace all hyperlinks with local path to the downloaded package. Finally, execute the installation script. The local repository server will resolve all packages and dependencies needed during installation.

Manual installation

If your only option is to manually install all packages needed, then you will need to first download all the prerequisite packages from a machine with internet access. Then, as each package is installed, you will need to make a note of the dependencies required. This will be an iterative process in order to find all the dependencies that are needed to complete the installation.

To prepare for manual installation, an internet-accessible machine is initially needed to download all the required packages. This machine should mirror the environment of the deployment server. A mirrored environment will accurately resolve package dependencies. Use the DNF Download Plugin (dnf-plugins-core) to retrieve packages.

sudo dnf download –resolve <package-name>

The command structure above will download the main package and any dependencies that is required. Dependencies are dictated by the Linux environment. If the deployment server has a very different Linux environment than the download machine, then resolving package dependencies can be a tedious process.