https://bz.apache.org/bugzilla/show_bug.cgi?id=64831
--- Comment #11 from Michael Osipov <[email protected]> --- (In reply to Felix Schumacher from comment #9) > Created attachment 37782 [details] > Log debug information about loaded certificates > > Change names of variables and capitalization of Log messages as suggested by > Michael. Changes work for me except for the last remaining comments. > While testing this feature, I came to the conclusion, that something like a > Cert-Debug-Sampler would be a really good idea. Maybe we could add a > getCertsInfo method to the JMeterKeyStore, that gets initialized on first > loading of the keystore? This sounds like a plan, but I see that the "SSL Manager" needs to be addressed first. It is not really possible to select the KeyStore type. For instance, I do use Windows-MY with my smartcard but have to launch JMeter via terminal and a system property which is ugly. SSL Manager should either be a configuration element at top level or least a dialog which provides three fields: (1) KeyStore type (2) optional path (file picker) (3) optional password (input box) instead of a mere file picker Windows-MY does not require (2) and (3). The reason why both JKS and PKCS 12 work is this line: > keystore.type.compat=true in/usr/local/openjdk8/jre/lib/security/java.security -- You are receiving this mail because: You are the assignee for the bug.
