-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Cert Auth instead of PSK? #118
Comments
Do you want it because you want to use AWS IoT? |
I want to use it at work to connect from containers running on EdgeDevices to our fog servers running mosquitto and vernemq. In Production we would rather want to have the gateways login with their signed certs using FQDN as user than have PSK credentials stored on them. Could that work with MqttNet? |
I added support for client certificates, initial tests look promising. You can set the certificates at: Please tell me if you run into any trouble |
Very cool!
I validated the broker settings with nodered and checked, with which settings I can successfully connect and with which I dont. If I add Server crt, client crt and client key to MQTT Explorer, I can connect, like I should. In UI under Advanced Client Cert and Key Buttons go to the same line when only one of them is configured. If you configure Client Key first, it will be displayed below Client Cert Button, that could be irritating. Excellent! Thx a lot for implementing! |
The UI still needs some love, but I thought you would appreciate the prototype 😉 |
Yes absolutly! I very much appreciate it. Now I need to find out how to enable PSK and Client Cert Auth on VerneMq and mosquitto at the same time. |
Will be released for all platforms in 0.3.2, currently build into Ubuntu snap releases and 0.3.1 pre-release. |
Released with v0.3.5. |
Would it be possible to give an option to also attach a Client public key to authenticate?
The text was updated successfully, but these errors were encountered: