Skip to content
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

Adding Support for MQTT with TLS Using Certificates in FUXA #854

Closed
eduardojvieira opened this issue Jun 19, 2023 · 3 comments
Closed

Adding Support for MQTT with TLS Using Certificates in FUXA #854

eduardojvieira opened this issue Jun 19, 2023 · 3 comments
Labels
feature New feature

Comments

@eduardojvieira
Copy link

Hello frangoteam,

I've been using FUXA in my recent project to visualize and render data using MQTT. I really appreciate the functionality it offers; however, I have encountered a situation where I need to establish a secure MQTT connection using SSL certificates (CA cert, Client cert, and client key).

Currently, FUXA supports MQTT connections with authentication via username and password. While this works fine in many situations, it falls short when advanced security is required and secure connections need to be established via SSL/TLS using certificates.

The underlying MQTT.js library which FUXA uses for MQTT connections already has support for TLS connections (see example here: https://github.com/mqttjs/MQTT.js/tree/main/examples/tls%20client). Therefore, I believe it would be a valuable feature addition to allow users to specify CA cert, Client cert, and client key within FUXA to take advantage of the secure MQTT with TLS provided by MQTT.js.

This enhancement would not only increase the level of security in the application, but also broaden the scope of projects that could utilize FUXA.

Please consider this feature request for a future release. I believe it would be a great asset for many developers dealing with secure IoT applications and more.

Thank you for your time and consideration.

Best regards,
Eduardo

@unocelli unocelli added the feature New feature label Jun 21, 2023
@unocelli
Copy link
Member

Hi, doesn't look complicated, how many and what types of certificates should the GUI allow you to configure?

@eduardojvieira
Copy link
Author

Normally three files are needed to establish the connection using TLS:

The CA certificate (CA Root)
The client certificate
client private key

@unocelli
Copy link
Member

unocelli commented Jul 9, 2023

I’m going to close this as resolved. let me know if you have any issues.

@unocelli unocelli closed this as completed Jul 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

No branches or pull requests

2 participants