This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
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?