The SCM documentation states that "if your DBMS is SQL Server, the web interface uses SQL Server Authentication for its database connection because the SQL Server JDBC driver supports SQL Server Authentication ONLY" (see Find the SQL Server Authentication User for Database User). Microsoft has created a work-around for this limitation which can be implemented with SCM to allow you to use Windows Authentication to access your SQL Server database with the SCM Web Interface (Harweb).
How to enable Windows Authentication for SQL Server with SCM Web Interface (Harweb)?
Harvest Software Change Manager 12.1 and higher
Windows OS, SQL Server database
This example scenario shows how to do this when the Harvest broker, SQL Server, and Tomcat hosting Harweb are all on the same server, and in hdbsetup, the Harvest database connection was set up using Windows authentication. The key to this configuration is to use the same Windows account when configuring how Harvest will connect to the database, and when configuring the userid that will be used to start the Tomcat and Harvest Broker services.
Microsoft has provided the following work-around to implement Windows Authentication to SQL Server via the JDBC 3.0 Driver. Details can be found here under the title "Building the Connection URL". See especially the section on Connecting with integrated authentication on Windows.
More on installing Harweb is found here: Install CA Harvest SCM Web Interface
More information on hdbsetup is found here: The hdbsetup Database Configuration Utility