You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/07/04 18:16:47 UTC
DO NOT REPLY [Bug 21344] New: -
Https missing configuration to handle p12 certificates
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21344>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21344
Https missing configuration to handle p12 certificates
Summary: Https missing configuration to handle p12 certificates
Product: JMeter
Version: 1.8.1
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: HTTP
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: lmedioni@sqli.com
It should be said in the documentation or in the comments of jmeter.properties
that to properly handle a .p12 certificate mag you should add
"
javax.net.ssl.trustStore=C:/.../MyCertMag.p12
javax.net.ssl.keyStoreType=pkcs12
"
to jmeter.properties, after having uncommented the usual
"
ssl.provider=com.sun.net.ssl.internal.ssl.Provider
ssl.pkgs=com.sun.net.ssl.internal.www.protocol
"
(second line not explained in the JMeterdocumentation...)
Otherwise there is a bug (invalid keystore format) because the JMeter does not
set the mag type (even when using the SSLManager and choosing a .p12!) and rely
on the default (= pks = error when using a .p12).
This could avoid to other folks to spend 2 days looking for a solution, exactly
what I have done :)
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org