wood burning stoves 2.0*
The moose likes JDBC and the fly likes x509 driving me nuts! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "x509 driving me nuts!" Watch "x509 driving me nuts!" New topic
Author

x509 driving me nuts!

porch rat
Greenhorn

Joined: Jul 25, 2011
Posts: 1
Hi all.

I've recently been trying to implement x509 authentication through the JDBC. (MySQL Connector J)

I'm using self-signed certificates. When I have the MySQL user set to "require x509" on the server I can connect just fine using a MySQL client. The minute I load the certificates into the truststore and keystore though I get this:

Access denied for user 'foo'@'bar' (using password: YES)


Obviously the name of the user and it's source have been changed to protect the innocent.

Can anyone offer reasons as to why my certificates would work when connecting with the MySQL client but not with the JDBC?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: x509 driving me nuts!