As many others have said, thanks for a great tool, it has really helped us with development.
We would like to suggest to users of our software that they use MQTT Explorer, though we won't distribute it ourselves. But we are encountering problems when connecting with MQTT Explorer to a mutual TLS secured HiveMQ 4.6.4 broker. We do not encounter the same issues when connecting from .NET Framework or .NET Core.
I can provide the certificates / keys / passwords (currently self-signed ones for development purposes, no CA involved) if you want to reproduce.
Normally, our certificates and keys are password-protected, and I can see nowhere in MQTT Explorer to set those passwords. So I tried this with no-password cert/key combinations too, but I still get exactly the same exception. So it doesn't look like cert/key password is the trigger.
Could you perhaps help our understanding? Perhaps provide examples of how to create cert/key pairs which do not cause issues with mutual TLS on MQTT Explorer?
Hi Thomas
As many others have said, thanks for a great tool, it has really helped us with development.
We would like to suggest to users of our software that they use MQTT Explorer, though we won't distribute it ourselves. But we are encountering problems when connecting with MQTT Explorer to a mutual TLS secured HiveMQ 4.6.4 broker. We do not encounter the same issues when connecting from .NET Framework or .NET Core.
I can provide the certificates / keys / passwords (currently self-signed ones for development purposes, no CA involved) if you want to reproduce.
Normally, our certificates and keys are password-protected, and I can see nowhere in MQTT Explorer to set those passwords. So I tried this with no-password cert/key combinations too, but I still get exactly the same exception. So it doesn't look like cert/key password is the trigger.
Could you perhaps help our understanding? Perhaps provide examples of how to create cert/key pairs which do not cause issues with mutual TLS on MQTT Explorer?
Thanks Riaan Swart