A recent bug-fix in OpenJDK 1.8.0_191 and later versions may cause problems for customers using the Java Unity Integration Toolkit in conjunction with any OpenJDK implementations. Previously, OpenJDK did not require certain parameters to be set in order to pass NTLM credentials on from the integration to OnBase. Until jdk1.8.0_191, a default NTLM authentication callback existed which was instrumental in the authentication process, however the default behavior has since been changed and that callback was removed. In order to activate it, the highlighted line must be changed from "disabled" to one of the other two options in the .NET properties configuration file located in your [JAVAHOME]/lib directory:
# Transparent NTLM HTTP authentication mode on Windows. Transparent authentication
# can be used for the NTLM scheme, where the security credentials based on the
# currently logged in user's name and password can be obtained directly from the
# operating system, without prompting the user. This property has three possible
# values which regulate the behavior as shown below. Other unrecognized values
# are handled the same as 'disabled'. Note, that NTLM is not considered to be a
# strongly secure authentication scheme and care should be taken before enabling
# this mechanism.
#
# Transparent authentication never used.
#jdk.http.ntlm.transparentAuth=disabled
#
# Enabled for all hosts.
#jdk.http.ntlm.transparentAuth=allHosts
#
# Enabled for hosts that are trusted in Windows Internet settings
#jdk.http.ntlm.transparentAuth=trustedHosts
#
jdk.http.ntlm.transparentAuth=allHosts
If you prefer to use trusted hosts, be sure to add the URL to your list of trusted sites in Windows.
