Changing the SQL DB connection from Windows Authentication to Local SQL Account Post Install

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

Steps to change the SQL DB connection from using Windows Authentication to using local SQL Account (e.g. sa) post installation of App Control

Environment

• App Control Server: All Supported Versions
• Single Tier Environment

Resolution

Important Single Tier Environment Only These steps are not supported for Two Tier environments. Two Tier environments require a Windows account that both the remote SQL Server and IIS can authenticate.

1. Log in to the application server as the Carbon Black Service Account.
   1. If an App Control Agent is on the system, temporarily stop and unload it.
   2. Temporarily stop the App Control Server and App Control Reporter services.
2. Copy and backup the following files from the App Control Server installation directory to another folder

   C:\Program Files (x86)\Bit9\Parity Server\WSProxy.config
   C:\Program Files (x86)\Bit9\Parity Server\Reporter\WSProxy.config
   C:\Program Files (x86)\Bit9\Parity Server\Reporter\ParityReporter.exe.config
   C:\Program Files (x86)\Bit9\Parity Console\API\Web.config
   C:\Program Files (x86)\Bit9\Parity Console\WebUI\html\Dashboard\Web.config
   C:\Program Files (x86)\Bit9\Parity Console\WebUI\include\DataObject.ini
   Optional: C:\Program Files (x86)\Bit9\Integrations\CheckPoint\bin\bit9.dsn
   Optional: C:\Program Files (x86)\Bit9\Integrations\FireEye\listener\Web.config

3. Edit the WSProxy.config files and ParityReporter.exe.config file

   C:\Program Files (x86)\Bit9\Parity Server\WSProxy.config
   C:\Program Files (x86)\Bit9\Parity Server\Reporter\WSProxy.config
   C:\Program Files (x86)\Bit9\Parity Server\Reporter\ParityReporter.exe.config

   • Locate the following line:

     <add key="ConnectionString" value="Integrated Security=SSPI; server=SQLSERVER\SQLINSTANCE; database=das" />

   • Change the line to use SQL authentication and specify the relevant Username and Password:

     <add key="ConnectionString" value="Trusted_Connection=No; uid=userhere; pwd=passwordhere; server=SQLSERVER\SQLINSTANCE; database=das" />

4. Edit the 2 Web.config files

   C:\Program Files (x86)\Bit9\Parity Console\API\Web.config
   C:\Program Files (x86)\Bit9\Parity Console\WebUI\html\Dashboard\Web.config

   • Locate the following line:

     <add name="ConnectionString" connectionString="Integrated Security=SSPI; server=SQLSERVER\SQLINSTANCE; database=das;" providerName="System.Data.SqlClient" />

   • Change the line to use SQL authentication and specify the relevant Username and Password:

     <add name="ConnectionString" connectionString="Trusted_Connection=No; uid=userhere; pwd=passwordhere; server=SQLSERVER\SQLINSTANCE; database=das;" providerName="System.Data.SqlClient"/>

5. Edit the DataObject.ini file

   C:\Program Files (x86)\Bit9\Parity Console\WebUI\include\DataObject.ini

   • Locate the following line:

     database_das     ="sqlsrv://SQLSERVER\SQLINSTANCE/das"

   • Change the line to use SQL authentication and specify the relevant Username and Password:

     database_das     ="sqlsrv://user:password@SQLSERVER\SQLINSTANCE/das"

   • For example:

     database_das     ="sqlsrv://sa:{Password1234}@CBSQL01\MSSQLSERVER/das"

6. Edit the two DSN files

   C:\Program Files (x86)\Bit9\Parity Server\shepherd.dsn C:\Program Files (x86)\Bit9\Parity Server\install.dsn

   • Each should be adjusted to specify SQL authentication using the relevant Username and Password:

     [ODBC]
     DRIVER=SQL Server Native Client 11.0
     UID="loginhere"
     Trusted_Connection=No
     DATABASE=das
     SERVER=SQLSERVER\SQLINSTANCE
     pwd="passwordhere"

7. Start the App Control Server and App Control Reporter services.
8. Log in to the Console and verify Agents are beginning to reconnect.
   • Load and start the Agent if it was temporarily stopped.