• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

x509 driving me nuts!

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
reply
    Bookmark Topic Watch Topic
  • New Topic