Hello, In fact it seems this feature only works with HTTPCLient 3.1. See: - https://issues.apache.org/bugzilla/show_bug.cgi?id=52871
Thank you Regards Philippe M. http://www.ubik-ingenierie.com On Fri, Mar 9, 2012 at 12:56 PM, <[email protected]> wrote: > Philippe, > > Thanks. I'll try again later, but it seems like I only get the multiple > certs behavior with HTTPClient 3.1, and not HttpClient 4? > > Jim > > > ---- Philippe Mouawad <[email protected]> wrote: > > Hello, > > > > You can achieve the first by setting: > > - HTTPClient 3.1 or 4 as implementation > > - setting https.use.cached.ssl.context=false > > > > Regards > > Philippe M. > > http://www.ubik-ingenierie.com > > > > > > > > On Fri, Mar 9, 2012 at 7:59 AM, <[email protected]> wrote: > > > > > Hi, > > > > > > I am using Jmeter 2.6, and want to have the HTTPS requests that Jmeter > > > sends use different client certificates that I have in a JKS keystore > which > > > has 3 client certs/keys in it.. > > > > > > I've been able to configure a test plan that works, but it is only > sending > > > one of the certs in the JKS. I added a Keystore configuration and set > > > start to 1 and last to 3, but when I run the test plan, I can see that > it's > > > still using only the one client cert. > > > > > > Besides adding the Keystore Configuration to the thread group, is there > > > something else that I need to do to get Jmeter to use the client certs, > > > one-by-one for each test request? > > > > > > Thanks, > > > Jim > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > -- > > Cordialement. > > Philippe Mouawad. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cordialement. Philippe Mouawad.
