Closed kindredally closed 3 years ago
do you have an example of what you would like to do, and why the root certificates included do not suffice?
It is because MQTT brokers often require it. The AWS broker does support user id + password , only authentication. I don't have the code in front of me, but if you search on async esp8266 mqtt aws or look in the Bear header file it mentions mqtt and adding the certificate but I can't see how the framework could coexist.
On Thu., Apr. 29, 2021, 10:32 a.m. Maakbaas, @.***> wrote:
do you have an example of what you would like to do, and why the root certificates included do not suffice?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/maakbaas/esp8266-iot-framework/issues/105#issuecomment-829288425, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATU2BJ7QL4MJBUPM34PF5FDTLFUW3ANCNFSM43Z52O2A .
Right now, no MQTT related functionality is implemented. However, this framework does not prevent you from using any code, default functions or libraries, so whatever you aim to do should be possible with your own code on top of or next to the framework.
You are always welcome to propose new added functionality to add MQTT for instance.
Unless you can show a specific example where this framework causes an issue I will close this thread for now.
Hi. The system is generating certificates, but is there a way to also include your own ones? I want to access Amazon's mqtt server which requires three custom keys to authenticate. The pubsub library won't work because it is not async...although it works on its own. Using the async mqtt library seems like a good idea except the certificates don't seem compatible.