Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For known limitations using the SSH Job to connect to a Windows Remote Host see Limitations when using SSH jobs for Windows.

Known Issues

Connecting to a Solaris machine

Sometimes while connecting to a Solaris machine an error occurs which states "java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 2048 (inclusive)".

This Java-Security Issue is documented here and here.

To workaround this Issue you can do as follows:

  • First download the following jars from BouncyCastle at https://www.bouncycastle.org/latest_releases.html
    • bcprov-jdk15on-152.jar

    • bcprov-ext-jdk15on-152.jar

  • Copy those jars to your ${JAVA_HOME}/jre/lib/ext/ folder
  • Edit the ${JAVA_HOME}/jre/lib/security/java.security properties file
    • Add the JCE provider you’ve just downloaded
      • Search for security.provider in the configuration and add the BouncyCastleProvider as the second provider

After the changes your configuration should look like this:

 

Code Block
languagebash
security.provider.1=sun.security.provider.Sun
security.provider.2=org.bouncycastle.jce.provider.BouncyCastleProvider
security.provider.3=sun.security.rsa.SunRsaSign
security.provider.4=sun.security.ec.SunEC
security.provider.5=com.sun.net.ssl.internal.ssl.Provider
security.provider.6=com.sun.crypto.provider.SunJCE
security.provider.7=sun.security.jgss.SunProvider
security.provider.8=com.sun.security.sasl.Provider
security.provider.9=org.jcp.xml.dsig.internal.dom.XMLDSigRI
security.provider.10=sun.security.smartcardio.SunPCSC
Note

Make sure to add the BouncyCastleProvider as the second Provider and adjust the numeration.

  • If you add the Provider as the first, the default Java JCE can be broken.
  • If you add the Provider as the last one, it can happen that Java doesn´t recognizes it.