Right now, there seems to be a problem with MQTT over tls on the broker's end (broker doesn't trust the client's certs). We could "solve" this by allocating specific domain names to each teller instance (like teller1.openx.solar) but this would be cumbersome and extra work to do on our end. We would need to have a mechanism to transmit the cert to the broker and the broker should have an endpoint where it authenticates an openx caller (by making a call to the openx API) and then storing the cert in its client cert list. Depends on the broker implementation, but I think a fix targeted towards mosquitto should be enough.
Right now, there seems to be a problem with MQTT over tls on the broker's end (broker doesn't trust the client's certs). We could "solve" this by allocating specific domain names to each teller instance (like
teller1.openx.solar
) but this would be cumbersome and extra work to do on our end. We would need to have a mechanism to transmit the cert to the broker and the broker should have an endpoint where it authenticates an openx caller (by making a call to the openx API) and then storing the cert in its client cert list. Depends on the broker implementation, but I think a fix targeted towards mosquitto should be enough.