JDBC SP3 and SSL

Hello all,
If I enable SSL on my SQL Server (using the Force Protocol Encryption in
Server Network Utility) and then use JDBC SP3 to connect (and Java 5 Update
2), will the connection succeed? If the current version of Microsoft's JDBC
Driver for SQL Server won't make a SSL connection, are there plans on a
future version having this capability?
The reason I ask is because we have one application that uses JDBC to
connect to SQL Server and it has to use Microsoft's JDBC Driver in order to
work, so using a Type 3 JDBC driver isn't an option for us.
Thanks,
Jason
Why does your application have to use the MS driver? There are a lot of
commercial type 4 drivers out there and a pretty good open source one,
too. All of these support SSL.
Alin,
The jTDS Project.
|||Alin,
The application I'm referring to is a purchased application, and I believe
it is coded to use the Microsoft JDBC driver. At least that is what the
installation instructions lead me to believe.
Thanks,
Jason
"Alin Sinpalean" wrote:

> Why does your application have to use the MS driver? There are a lot of
> commercial type 4 drivers out there and a pretty good open source one,
> too. All of these support SSL.
> Alin,
> The jTDS Project.
>
|||Jason Delaune wrote:
> Alin,
> The application I'm referring to is a purchased application, and I
believe
> it is coded to use the Microsoft JDBC driver. At least that is what
the
> installation instructions lead me to believe.
Usually applications are coded to use the JDBC specification. Relying
on non-standard features of particular implementations is not a good
idea. If that's the case then you're out of luck.
You could still try another driver, though. In 90% of the cases it
works.
Alin.
|||Alin,
Which driver(s) would you recommend that supports connections to SQL Server
using SSL?
Thanks,
Jason
"Alin Sinpalean" wrote:

> Jason Delaune wrote:
> believe
> the
> Usually applications are coded to use the JDBC specification. Relying
> on non-standard features of particular implementations is not a good
> idea. If that's the case then you're out of luck.
> You could still try another driver, though. In 90% of the cases it
> works.
> Alin.
>
|||I would of course recommend the open source jTDS JDBC driver (which I'm
a developer of); you can get it from http://jtds.sourceforge.net
There are also quite a few commercial drivers out there if you don't
trust open source, but they do cost a lot and are not necessarily
better. Just do a Google search and they will turn up.
Alin,
The jTDS Project.