Thanks to both of you Gordon and Jakub for your feedback.
Following Gordon's comment showing a different NSS version from mine
I've done some testing and it seems it is indeed down to the version
of NSS. In particular it looks like NSS 3.28 does not work and NSS
3.31 does work.
Here's what I did
I did some more digging through my old work emails. We had a customer with
this kind of problem in June 2015. At that time I was able to reproduce
this behaviour on Linux (I believe they were Windows users, so it should
have affected also Windows). The problem was exactly the same as described
by C
On 21/08/17 21:46, Chris Richardson wrote:
Hi,
I've encountered an issue with the C++ broker (1.36) where it appears
that multiple connections within the same process using SSL client
auth do not use the "ssl-cert-name" property provided when the
connection instance is created. Rather, it appear
This is definitely not new in 1.36. I think this is present "since the
beginning". :-(
If I remember correctly the problem was that the NSS library which handles
the SSL certificates is initialised only once even when you create multiple
connections. I was quite sure this was already discussed in
Hi,
I've encountered an issue with the C++ broker (1.36) where it appears
that multiple connections within the same process using SSL client
auth do not use the "ssl-cert-name" property provided when the
connection instance is created. Rather, it appears the second
connection will use auth details
