Re: Multiple connections with ssl client auth does not work as expected

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

Multiple connections with ssl client auth does not work as expected

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