Hello, I have a java keystore (.jks file) with 3 client certs.I have a test plan with 3 independed threads (thread 1-3)My test plan runs the threads successively means thread 1 then 2 then 3 every time i run my test.I have one Keystore Configuration element placed directly under my test plan.The configuration is as follow:preload: falsevariable: none start: 0end: 2 Perfect. Now when i start my test the keystore will be created with total of 3 aliases (because i have 3 certs).Then in thread 1 i do a login to my server using https and the first cert with index [0] will be sent to my server and the login works perfect.Now i just do a simple http get request to my server and it works perfect. Then i do a logout. Now the next thread starts again with a login to my server and now the next cert with index [1] will be used. Again it works perfect and the same with thread 3 and cert on index [2]. Perfect. BUTWhen i deactivate e.g. thread 1 and don't want to run it but want to start with thread 2 then this time the login will be done with cert [0].Of course this is because the keystore is loaded again with 3 certs and it will pick cert [0].
So my idea was to create 3 keystore configurations for each thread like this.Thread 1 - keystore configuration:start: 0end: 0 Thread 2 - keystore configuration:start: 1end: 1 Thread 3 - keystore configuration:start: 2end: 2 So with this i could deactivate thread 1 and let jmeter only execute thread 2 and thread 3 and then the cert on index [1] for thread 2 and on index [2] for thread 3 will be used and thread 1 and cert [0] will be skipped.But this does not work because (what i think is) jmeter do create only one keystore configuration instance per test plan and load the whole jks file. Then all you can do is "looping" through the cert index.I can't use the variable for cert alias because my http request do not sent any variable for login. The server get the loginname directly from the cert cn name. Anyone got any idea how i could manage this? brgeorge
