Users unable to login to the Monitor Console after Oracle Java 8u201 update - "Unable to connect to the Application Service" message

The Monitor Console will be unable to login to the services when launched via JNLP (WebStart).

The latest update to Oracle Java 8 (8u201) disables anonymous TLS cipher suites by default; the Monitor Console requires the use of an anonymous cipher suite.

Resolution

Do not install the Oracle Java 8u201 update on your client machines until you have upgraded your services to the 8.1.00.245D Server Fix Pack (or a later Server Fix Pack) and installed the standalone Monitor Console on your client machines.

If your client machines have already been upgraded to Oracle Java 8u201, there are three ways to resolve the issue:

Option 2 - On each client machine, edit the lib\security\java.security file in your JRE installation. Find the line that starts with the text jdk.tls.disabledAlgorithms, and remove the text “, anon”.

For example, find the following line:

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \  
EC keySize < 224, 3DES_EDE_CBC, anon, NULL

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \  
EC keySize < 224, 3DES_EDE_CBC, NULL

Note:
Option 3 is the recommended way forward as in later versions than Java 8, Oracle Java will no longer provide the Java WebStart functionality which previously was used to launch the Monitor Console. By installing The standalone Monitor Console no longer relies on this functionality to be available.

For the time being, running the Monitor Console as a Java WebStart application is still supported, even after Server Fix Pack D (or later) got applied, but its use is deprecated. Still either one of the actions described in Option 1 and Option 2 are required, even after applying the Fix Pack.