Summary: | SSL Manager does not handle multiple client certificates | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Laurent Medioni <lmedioni> |
Component: | HTTP | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | p.mouawad |
Priority: | P3 | ||
Version: | 1.9.RC3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Laurent Medioni
2003-08-18 11:51:39 UTC
Setting correct severity. I'm not familiar with the SSL Manager or key stores, but I have the feeling that this can be easily worked around by using a key store containing only the desired key. Plus of course correcting the manuals. Can someone who knows confirm this and possibly fix or downgrade severity to Minor? Yes, it can handle one certificate properly (only the first one unfortunately for me). The documentation has to be corrected if multi-cert is not a feature to be retained. But it would be great to be able to allocate a different certificate (or at least a reasonable pool of them) to each thread. Otherwise JMeter does not stress test the whole process of authentication because of the various cache levels in the systems. I also had a similar problem, and circumvented it by having different configuration files (jmeter.properties.xxx) for every certificate, and using the different configuration files in different instances of jmeter (starting with jmeter -p jmeter.properties.xxx). Of course, this is quite memory- consuming, but it works. This is currently a restriction. The documentation has been updated accordingly. It would be useful to support multiple certificates at some point I believe the solution of this case was implemented in this: https://issues.apache.org/bugzilla/show_bug.cgi?id=52033 *** This bug has been marked as a duplicate of bug 52033 *** This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1198 |