Encrypted communication with JDBC driver?

We need encrypted communication with a SQL Server 2005 but I have found no
documentation on how to do this with the JDBC driver. that is; the
communication is encrypted, no problem, but the JDBC driver can't connect.
Does anyone have any knowledge on this?
Thanks,
Thor Egil LeirtroYou can encrypt the data first and then store them in the database.
Thor Egil Leirtr=F8 wrote:
> We need encrypted communication with a SQL Server 2005 but I have found no
> documentation on how to do this with the JDBC driver. that is; the
> communication is encrypted, no problem, but the JDBC driver can't connect.
> Does anyone have any knowledge on this?
>=20
> Thanks,
> Thor Egil Leirtro|||This is part of a large system so encrypting the data in the DB is not an
option. The requirement is to encrypt the communication to the database.
This seems to be working out of the box with the OLEDB drivers, but I can
find no support for it in the JDBC driver.
Thor Egil Leirtro
"Jet Mah" <jetmah@.gmail.com> wrote in message
news:1150735621.329206.99550@.u72g2000cwu.googlegroups.com...
You can encrypt the data first and then store them in the database.
Thor Egil Leirtr wrote:
> We need encrypted communication with a SQL Server 2005 but I have found no
> documentation on how to do this with the JDBC driver. that is; the
> communication is encrypted, no problem, but the JDBC driver can't connect.
> Does anyone have any knowledge on this?
> Thanks,
> Thor Egil Leirtro|||Thor Egil Leirtr wrote:

> This is part of a large system so encrypting the data in the DB is not an
> option. The requirement is to encrypt the communication to the database.
> This seems to be working out of the box with the OLEDB drivers, but I can
> find no support for it in the JDBC driver.
That is correct. The JDBC driver doesn't yet have support
for encrypted transmission.
Joe Weinstein at BEA Systems

> Thor Egil Leirtro
> "Jet Mah" <jetmah@.gmail.com> wrote in message
> news:1150735621.329206.99550@.u72g2000cwu.googlegroups.com...
> You can encrypt the data first and then store them in the database.
> Thor Egil Leirtr wrote:
>
>
>|||Thanks, that was what I suspected. If you have this from a reliable source,
we will have to find other ways.
Thor Egil Leirtro
"Joe Weinstein" <joeNOSPAM@.bea.com> wrote in message
news:4496E15C.5040300@.bea.com...
>
> Thor Egil Leirtr wrote:
>
> That is correct. The JDBC driver doesn't yet have support
> for encrypted transmission.
> Joe Weinstein at BEA Systems
>
>|||You can encrypt the data first and then store them in the database.
Thor Egil Leirtr=F8 wrote:
> We need encrypted communication with a SQL Server 2005 but I have found no
> documentation on how to do this with the JDBC driver. that is; the
> communication is encrypted, no problem, but the JDBC driver can't connect.
> Does anyone have any knowledge on this?
>=20
> Thanks,
> Thor Egil Leirtro|||This is part of a large system so encrypting the data in the DB is not an
option. The requirement is to encrypt the communication to the database.
This seems to be working out of the box with the OLEDB drivers, but I can
find no support for it in the JDBC driver.
Thor Egil Leirtro
"Jet Mah" <jetmah@.gmail.com> wrote in message
news:1150735621.329206.99550@.u72g2000cwu.googlegroups.com...
You can encrypt the data first and then store them in the database.
Thor Egil Leirtr wrote:
> We need encrypted communication with a SQL Server 2005 but I have found no
> documentation on how to do this with the JDBC driver. that is; the
> communication is encrypted, no problem, but the JDBC driver can't connect.
> Does anyone have any knowledge on this?
> Thanks,
> Thor Egil Leirtro|||Thor Egil Leirtr wrote:

> This is part of a large system so encrypting the data in the DB is not an
> option. The requirement is to encrypt the communication to the database.
> This seems to be working out of the box with the OLEDB drivers, but I can
> find no support for it in the JDBC driver.
That is correct. The JDBC driver doesn't yet have support
for encrypted transmission.
Joe Weinstein at BEA Systems

> Thor Egil Leirtro
> "Jet Mah" <jetmah@.gmail.com> wrote in message
> news:1150735621.329206.99550@.u72g2000cwu.googlegroups.com...
> You can encrypt the data first and then store them in the database.
> Thor Egil Leirtr wrote:
>
>
>|||Thanks, that was what I suspected. If you have this from a reliable source,
we will have to find other ways.
Thor Egil Leirtro
"Joe Weinstein" <joeNOSPAM@.bea.com> wrote in message
news:4496E15C.5040300@.bea.com...
>
> Thor Egil Leirtr wrote:
>
> That is correct. The JDBC driver doesn't yet have support
> for encrypted transmission.
> Joe Weinstein at BEA Systems
>
>|||Thor Egil Leirtr wrote:

> Thanks, that was what I suspected. If you have this from a reliable source
,
> we will have to find other ways.
> Thor Egil Leirtro
Check the driver docs:
"When using the JDBC driver to communicate with a SQL Server database, the
communication is not encrypted or signed. To help protect the communication
with the server, you should secure the channel using IPSEC."
Joe Weinstein at BEA Systems

> "Joe Weinstein" <joeNOSPAM@.bea.com> wrote in message
> news:4496E15C.5040300@.bea.com...
>
>

Encrypted Communication between two SQL 2000 Servers

How can i obtain encrypted communication between two SQL
Servers 2000 using Replication?
ThanksSee the following kb articles on setting up protocol encryption.
This will encrypt all the traffic, not just Replication related calls.
316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
http://support.microsoft.com/?id=316898
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||OK, thanks. In my case i should Force Protocol Encryption on the server beca
use if i use it on the client... How can i indicate to the Subscriber that t
he comunication with the Publisher must be Encrypted without using Force Pro
tocol Encryption in the Sub
scriber Server?|||It's either or. If you want ALL communication to the Server/Publisher
encrypted, then enable it on the server.
If you only want communication from the Subscriber to the Publisher
encrypted, then only enable it there. So, you only turn it on in one
place, at the server or at the client. If the client has this bit turned
on, the server knows how to handle the request when the client connects.
The client needs to Trust the same CA that issued the cert. This is all
documented in the kb articles I forwarded.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.