Bug #87064 Client Certificates with MySQL Monitor and MySQL Monitor Agent
Submitted: 13 Jul 2017 18:07 Modified: 1 Aug 2017 19:32
Reporter: Jason Miele Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Configuration Severity:S4 (Feature request)
Version:3.4.2 OS:Linux
Assigned to: CPU Architecture:Any
Tags: SSL

[13 Jul 2017 18:07] Jason Miele 
Description:
Feature Request: Client Certificates with MySQL Monitor and MySQL Monitor Agent 

 In the MySQL Monitor Agent configuration we would like to define: keystoreFile and keystorePass (to work in conjunction with the existing ssl-ca-keystore-path and ssl-ca-keystore-password) 

 In the MySQL Monitor configuration we would like to define the following variables, for Tomcat: clientAuth, sslProtocols, keystoreFile, keystorePass, truststoreFile, truststorePass, sslEnabledProtocols, sslProtocols

How to repeat:
Feature Request: Client Certificates with MySQL Monitor and MySQL Monitor Agent 

 In the MySQL Monitor Agent configuration we would like to define: keystoreFile and keystorePass (to work in conjunction with the existing ssl-ca-keystore-path and ssl-ca-keystore-password) 

 In the MySQL Monitor configuration we would like to define the following variables, for Tomcat: clientAuth, sslProtocols, keystoreFile, keystorePass, truststoreFile, truststorePass, sslEnabledProtocols, sslProtocols