Answer by Andreas Rusch

Andreas Rusch — Fri, 22 Feb 2019 10:33:27 -0500

After a lot of research I finally found the cause of the problem:

With jre8_201 Oracle introduced (without mentioning it in the release notes, thanks very much!) a new authentication parameter (as security property) jdk.http.ntlm.transparentAuth in the JRE configuration file <jre_home>/lib/net.properties. It also sets the default value to disabled (other possible values are allHosts and trustedHosts), therefore completely disabling transparent authentication on Windows.

Possible solutions: So far I found two ways to get around the problem:

The obvious one is to change the setting in the net.properties file to allHosts (former default) or trustedHosts (a better recommendation).
The less obvious solution is to configure your jre8_201 runtime in the Java Control Panel in the Java tab -> View... Here you can add e.g. -Djdk.http.ntlm.transparentAuth=trustedHosts to the Runtime Parameters section.

Note that these are only client side solutions. I haven't found a solution to override this behavior from the server (in the JNLP file). I am not even sure if we can do that as this is a security property and there are more restrictions on setting them than normal system properties.

Hope it helps.

Answers to: Java 8 Update 201 Authentication window on Startup

Answer by Andreas Rusch