nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting up JIRA using windows authentication

Adam Moussa

When configuring JIRA through the web application on initial setup, the account I'm using to access Microsoft SQL 2012 DB is a service account, but I am getting an error in SQL that I cant connect using SQL Authentication, Server is configured for Windows Authentication only. Which that is the case on how SQL is configured due to STIGS, but I am using a AD Service account and not a SQL account.

Accepted answers

All comments

Alexey Matveev

Please read this article about setting up SQL Server:

https://confluence.atlassian.com/adminjiraserver071/connecting-jira-applications-to-sql-server-2012-802592195.html

I guess the user must be a database user. If you want to use Windows Authentication then you should setup a trusted SQL connection or you have to use Mixed Authentication Mode.

Adam Moussa

Due to our network I cant get to that link you suggested. Also the service account is a domain account and has DB Owner permissions to the SQL DB. Also have the service account running the Atlassian JIRA Service (tomcat8.exe)on the application server. I tried the other JIRA service and just get an OOPS page.

Alexey Matveev

As far as I know Jiira does not support domain accounts for sql server. You need to make a database user and setup a trusted SQL connection.

You can also use a workaround but there is a disclaimer about using it. Hopefully you have access to this page:

https://confluence.atlassian.com/jirakb/setup-windows-based-active-directory-authentication-with-sql-server-720407218.html

Andy Heinzer

Hi Adam,

I understand you are looking to use windows authentication when Jira connects to your MS SQL database. I am afraid that the KB article Alexey linked to was accurate for Jira at least up until the 7.5.0 release.

In the 7.5 version, Jira changed what database driver it is using in order to connect to MS SQL databases. In Jira 7.4.x and before versions, Jira is using the open source JTDS driver. However starting with 7.5 and higher versions, Jira is using the Microsoft driver.

As a result the syntax used to connect to a database for each of these drivers is slightly different. We have a KB to explain what steps were necessary when Updating JDBC URL for Microsoft SQL Server. Note that KB is designed for existing installations, and not as much for new installs like yours. But this detail I think is probably playing a role in why this documented work-around does not work for your fresh Jira 7.6 version. So we certainly need to update the work-around KB to reflect the changes in 7.6. I will look to update that once I have a clear solution here.

In the meantime, I can see a few different approaches you might be able to take in order to get around this:

Install a Jira 7.4.x version and follow that existing KB steps as a means to complete this install
We can try to adjust the syntax for the new Microsoft Driver Jira 7.5+ is using. The KB I linked to in this post notes that the syntax is as follows:
```
jdbc:sqlserver://[serverName[\instanceName][:portNumber]][;property=value[;property=value]]
```
as such, we can try to apply the same parameters just in the format of this new driver to see if that works. I think the url tag of the dbconfig.xml would look something like this:
```
jdbc:sqlserver://serverName\instanceName:portNumber;autoCommit=false;useNTLMv2=true;domain=domainName
```
I am not certain this will work as the previous users were not using this specific driver to connect Jira to MS SQL.
It might be possible to keep Jira on the 7.6 version, but then install the previous JTDS driver for Jira and use that instead. This way you could still follow the existing KBs steps. The problem here is that Jira 7.5 and higher does not ship with this old JTDS database driver natively anymore. You can download that driver separately from https://sourceforge.net/projects/jtds/files/jtds/1.3.1/ and then extract the .jar file into the $JIRAINSTALL/lib/ folder, from there you just need to set the $JIRAHOME/dbconfig.xml file to use the correct url and driver-class parameters
```
<url>jdbc:jtds:sqlserver://serverName:port/databaseName;autoCommit=false;useNTLMv2=true;domain=domainName</url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
```
And then save this file and restart Jira for these changes to take effect.

I think that any one of these three options could provide you a means to connect Jira with this specific, restricted SQL environment. Please let me know if you have any questions or concerns. I am interested to find out if you have success with any of these options.

Regards,
Andy

Andy Heinzer

After searching a bit more I came across another existing KB that explains this better and provides the next steps to follow: Using Integrated Security with MsSQL for Jira. This article explains in even more detail how to make this work with your version of Jira and older versions of Jira as well.

Andy

Adam Moussa

Andy,

I installed Jira 7.4, so I shouldn't have to download the driver correct?

Adam Moussa

Andy,

Also I tried the below config with specific information to the string in "". I left whats not enclosed in "" as it reads below. Is that correct?

<url>jdbc:jtds:sqlserver://"serverName:port"/"databaseName";autoCommit=false;useNTLMv2=true;domain="domainName"</url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

Gary Tingley

The "unsupported" workaround resulted in an error.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-core