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

Add support for MQTTS certificates #16

Open
wants to merge 3 commits into
base: development
Choose a base branch
from

Conversation

naimo84
Copy link

@naimo84 naimo84 commented Mar 21, 2022

Hey @coldfire84,

I'd like to share my small feature "Add support for MQTTS certificates" with you. Background, why I implemented this: I'm hosting your great Alexa Home Skill on my own server within kubernetes. As I don't wanna transfer my mqtt message via unencrypted mqtt, I decided to setup the MQTT Server with a TLS config :) Therefore the new properties are needed. Also because of k8s, I needed an opportunity to use an different port than 1883 or 8883. Of course I could use my LoadBalancer Config to bind to 1883, but out of simplicity I'm gonna use a NodePort :D

TL;DR
I hope it's ok for you, that I coded this on my own ;) It was an interesting journey on how k8s, mqtt and alexa smart home skill works 👍

Greets,
Benjamin

@coldfire84
Copy link
Owner

coldfire84 commented Mar 21, 2022

Thanks for the PR.

As I don't wanna transfer my mqtt message via unencrypted mqtt, I decided to setup the MQTT Server with a TLS config :)

To be clear - the public service using MQTT w/ TLS: the server presents a certificate that must be trusted by clients and enables a secure connection between the server and client. Communication via unencrypted MQTT/ TCP 1883 is blocked.

If I have understood correctly, the objective here is to enable Mutual TLS (mTLS)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants