In this case the integratedSecurity clause will be omitted from the JDBC connection string, and the username and password will need to be specified. To do this, the database must allow "SQL Server and Windows Authentication mode" - otherwise known as mixed mode. If points 1 and 2 cannot be met then you will need to use username/password authentication. If you wish to start the DevTest components as services and use Windows authentication then you need the following to be trueġ) the service account user MUST be network authenticated (that is it must be an AD user)Ģ) the SQL Server must be in the same domain as the user, or one that a trust relationship existsģ) The JDBC connection string must have the form jdbc:sqlserver:// servername=server_name integratedSecurity=true The use of SQL server is complicated by many factors over and above other databases.
=jdbc:sqlserver://NUNMA04W7A:1433 databaseName=REG801DB integratedSecurity=true # MS SQL Server using Windows Authenticationĭradis.db.=.SQLServerDriverĭradis.db.=jdbc:sqlserver://NUNMA04W7A.ca.com:1433 databaseName=ED801DB integratedSecurity=trueĭetails for the Registry: (site.properties) Here is an example of database details for the Enterprise Dashboard: (dradis.properties) The user and password is your Windows logon and you will have to specify your domain in the userid. Need to determine what authentication is needed before the database instance is created. The SQL Server Instance is set for Windows Authentication only, if needing SQL Server and Windows Authentication mode, choose the other Server authentication. You also need to add the integratedSecurity=true option at the end of your URL connection string. The dll needs to be copied to DEVTEST_HOME\lib\native. The dll you use depends on the JVM you are running, 32-bit or 64-bit.