This blocks a migration from mySQL and upgrade to the Jira 9. Could you please at least provide estimates on that feature?

Any update on using AD user accounts to authenticate in SQL from Jira running on Linux?  The latest version of Jira dropped support for our current SQL DB, so we have to migrate to a newer SQL DB version...

Any update on using AD user accounts to authenticate in SQL from Jira running on Linux?

iTDS driver worked like a charm. Now I'm kind of stuck. Considering switching off SQL Server.

Strongly doubt it, Windows Integrated Authentication only works on Windows, AFAIK.

Is workaround still relevant if I'm running Jira on Linux?

I ran into this issue while migrating my Dev Confluence instance from 5.8.4 to 6.6.0, and accordingly changing from the net.sourceforge.jtds.jdbc.Driver to the com.microsoft.sqlserver.jdbc.SQLServerDriver.

My workaround was to use the IntegratedSecurity=true property, paired with running the Service under the AD service account (it formerly ran using the Local System account). So ultimately, the "dbo" account in the SQL database and the Service are using the same ActiveDirectory login. This also means that the hibernate.connection.username and hibernate.connection.password parameters in the confluence.cfg.xml are now unused, I assume.

    <property name="hibernate.connection.url">jdbc:sqlserver://mydbserver:1433;database=Confluence;IntegratedSecurity=true</property>

Its pretty much best practise to use AD user accounts to authenticate in SQL from applications in a Windows infrastructure. So please fix this

I'd also like an update on this too please. 

Dear All, maybe you can give an update here? We have a customer and it's a customer security requirement that JIRA and Confluence is supporting "Active Directory authentication on SQL Server". What is the current status? Many thanks for your feedback!