Support SQLServer JDBC driver configured with NTLM

[KyleAure]

User Story:
As a user of Open Liberty and SQLServer I want to be able to use the Windows New Technology LAN Manager (NTLM) authentication scheme to authenticate my connection to my SQLServer database.

This protocol was added to the SQLServer driver in 2019: microsoft/mssql-jdbc#998
This protocol uses Active Directory to authenticate connections to a SQLServer database.
This protocol is considered less secure than kerberos.
Not currently supported by Open Liberty

open-liberty/dev/com.ibm.ws.jdbc.metatype/resources/OSGI-INF/metatype/metatype.xml

Lines 1212 to 1215 in 4865b7a

	<AD id="authenticationScheme" ibmui:group="Advanced" required="false" type="String" name="%authenticationScheme" description="%authenticationScheme.desc">
	<Option value="JavaKerberos" label="JavaKerberos"/>
	<Option value="NativeAuthentication" label="NativeAuthentication"/>
	</AD>

Things to consider:

• How will this authentication mechanism affect connection matching in the connection?
  • Specifically, when one DataSource has multiple auth-aliases?
    • The only auth data provided or cached is a username and password
  • Does the SQLServer Driver add any auth data to the thread context?
    • Based on the SQLServer JDBC driver no thread, or security context is created for NTLM
• Do we need to validate any configuration when this auth scheme is used?
  • No the SQLServer driver will validate the configuration for us and throw an error when necessary.

Testing:

• In order to test this functionality we will need the following:
  • SQLServer database configured to use NTLM (FAQ)
  • Active Directory server to authenticate against
  • Application server to perform database work with.