Configure secure connections for Microsoft SQL server

If Microsoft SQL Server requires a secure connection, complete the following steps (if Microsoft SQL Server does not require a secure connection, you can omit these steps):

1. Open CSA_HOME\jboss‑as\standalone\configuration\
standalone.xml in a text editor.

2. Locate the connection-url entry for the Microsoft SQL Server datasource and change ssl=request to ssl=authenticate.

   For example:

   <connection-url>
   jdbc:jtds:sqlserver://127.0.0.1:1433/example;ssl=requestauthenticate
</connection-url>

3. Save and close the file.

4. Import the Microsoft SQL Server Certificate Authority's root certificate into the Java truststore of Codar.

   1. Copy the Microsoft SQL Server Certificate Authority's root certificate to the Codar system. If necessary, contact your database administrator to obtain the Microsoft SQL Server certificate.

   2. On the Codar system, open a command prompt and run the keytool utility with the following options to create a local trusted certificate entry for the Microsoft SQL Server.

      On Windows:

      "CSA_JRE_HOME\bin\keytool" -importcert -trustcacerts
-alias mssqldb -keystore "CSA_JRE_HOME\lib\security\cacerts"
-file <c:\certfile_name.cer> -storepass <password>

      On Linux:

      CSA_JRE_HOME/bin/keytool -importcert -trustcacerts
-alias mssqldb -keystore CSA_JRE_HOME/lib/security/cacerts
-file </tmp/certfile_name.cer> -storepass <password>

      CSA_JRE_HOME is the directory in which the JRE that is used by Codar is installed.

      <c:\certfile_name.cer> on Windows or </tmp/certfile_name.cer> on Linux is the path and name of the Certificate Authority's root certificate for the LDAP server. The file extension may be .cer rather than .crt. You can also use a different value for -alias.

   3. At the prompt to import the certificate, type Yes.
   4. Press Enter.

   5. Restart Codar, see Restart Codar.