SSL Manager does not handle multiple client certificates

[asfimport]

Laurent Medioni (Bug 22510):
The documentation says:
"13.9.4 SSL Manager
...
The next time you run your test, the SSL Manager will examine your key store to
see if it has more than one key available to it. If there is only one key, SSL
Manager will select it for you. If there is more than one key, you will be
prompted to select the alias you wish to authenticate as.
"

I have a jks file containing several certificates for the required CA and
JMeter never prompts and always uses the first one...
I tried to remove the first one from my jks and then Jmeter uses the second
one, and so on...

Is the documentation up to date or is this a bug ?

Votes in Bugzilla: 1
Severity: major
OS: All

Duplicated by:

• Allowing multiple certificates (JKS) #2604

[asfimport]

Jordi Salvat i Alabart (migrated from Bugzilla):
Setting correct severity.

[asfimport]

Jordi Salvat i Alabart (migrated from Bugzilla):
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?

[asfimport]

Laurent Medioni (migrated from Bugzilla):
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.

[asfimport]

Thomas Fischer (migrated from Bugzilla):
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.

[asfimport]

Sebb (migrated from Bugzilla):
This is currently a restriction. The documentation has been updated
accordingly.

[asfimport]

Sebb (migrated from Bugzilla):
It would be useful to support multiple certificates at some point

[asfimport]

Julian Cesar (migrated from Bugzilla):
I believe the solution of this case was implemented in this: #2604

[asfimport]

@pmouawad (migrated from Bugzilla):
This bug has been marked as a duplicate of #2604