-
Notifications
You must be signed in to change notification settings - Fork 397
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
Added TLS support for MQTT connections. #2459
Added TLS support for MQTT connections. #2459
Conversation
…onfigurator - IOT-49
…Path and trustStorePassword, cleanup and formatting
io.openems.edge.controller.api.mqtt/src/io/openems/edge/controller/api/mqtt/Config.java
Outdated
Show resolved
Hide resolved
…rivate key and trust store in PEM format
…ate key as strings
Feature/cert as text
Thanks for updating! I fixed the build problems locally. Could you please give me write permissions on your branch? By the way, this PR relates to #1575. Unfortunately back then I did not get feedback from community to finalize the implementation. |
@sfeilmeier, Unfortunately, because the fork sits in an organization and not in a user-owned repo GitHub doesn't allow the setting to be turned on. I invited you directly to the fork so you can push the changes. |
@scootermon Thank you. I pushed changes. Could you have a quick look? From my side its ready to merge. |
@sfeilmeier Thanks for the review and your changes. For me, everything looks fine, connection to the MQTT test client works too. |
In order to use TLS with an MQTT connection, the user has to provide the path to the certificate (.cert.pem), private key (.private.key) and trust store (.der) files under "Controller Api MQTT" in the Apache Felix Web Console Configurator.
The functionality of this feature has been tested with an AWS MQTT test client.