I run Confluence on Linux platform and since the switch from jTDS to MS driver it won't work anymore. Cannot login. Even fresh install doesn't work. Do you guys have some test cases or maybe suggestions on how to make it work on Linux? Spent few days dancing around Kerberos configuration with no success. Have a ticket with you guys open but so far no clear answer. Thanks! 

When the suggestion says for Confluence Cloud ? Do you plan to bring in this for Server instance as well ?

Would like to also suggest Microsoft JDBC driver seriously be looked at for adoption.

1st Reason - It is open source now (https://blogs.msdn.microsoft.com/jdbcteam/2016/11/17/open-source-jdbc-maven/).

2nd Reason - It is very difficult for organizations needing high uptime and availability to still have to rely on JTDS driver as an option. It doesn't support any type of high availability (mirroring or always on groups) as other people have noted. Always On Availability Groups are continually being improved and would be huge win for peace of mind if adopting Atlassian products on SQL Server in the enterprise.

Love Atlassian products but it is very difficult to recommend spending enterprise level money for Data Center edition (with high availability front end) when one of the available database backends supported (SQL Server - which most enterprises have and readily deploy) doesn't allow for any high availability technology that was introduced in last 12 years due to JTDS driver.

Please enable Microsoft SQL JDBC for Confluence. We also use HCE DB for Confluence with Always On AG and the multisubnetfailover=true is not supported with JTDS. 

We are using AlwaysOn Availability groups for our MS SQL Servers, and jTDS doesn't seem to support it. It would be nice to have for DR\HA reasons.

Re: the 'Clustering' change in this issue:

Supporting database mirroring is very helpful even on Confluence installations that are not clustered (in the Atlassian sense).

I would point out that database mirroring is much easier to set up than other HA options in SQL server, such as failover clustering (which also requires shared storage and Enterprise editions of Microsoft Windows), and as a result it's a great HA option for smaller installations.

Basically, I'm saying that I hope the issue change is not a sign that this might be only supported in a Confluence cluster.

I got some troubles during these past two weeks, below is the guide to make Confluence use SSO:

https://confluence.atlassian.com/pages/viewpage.action?pageId=608731865&moved=true

A big thanks to bscholer@cshl.edu guide, which was indeed a key create the SSO guide .

Hey bscholer@cshl.edu

That guide is to authenticate with a domain account, the one to make it work with SSO will be created today , since the jtds driver we use does not support SSO due that missing dll (as per the link you send) I will need to add a different set of steps.

Once I'm done I will edit this feature so it main focus will be to support fail over since we will have the domain authentication/SSO covered.

That guide seems to be missing the part where you need ntlmauth.dll to make SSO work. I actually already wrote a guide for this about a month after my last comment on this issue:
http://www.briantist.com/how-to/jtds-ntlm-auth-confluence-sql-server/

I think it would make sense to remove Windows authentication as a reason for wanting MS JDBC support, since it's not necessary just for that.

However, automatic database failover is a pretty important part of having a robust installation, and jTDS does not support it.