Allow TahuClient to connect using client cert/private key
jlordiales opened this issue · 1 comments
jlordiales commented
It looks like today it is only possible to use username+password to connect from the TahuClient. Brokers like AWS IoT only allow connections via client cert/private keys so it would be nice to have that option as well.
All that would be needed is for the client to accept an optional SSLSocketFactory which could then be set in the client's MqttConnectOptions, similar to this example. Happy to submit a PR if you think this is worth doing.
wes-johnson commented
This is definitely worth doing. Just make sure you submit the PR against the develop branch and also sign the ECA before submitting it so I can accept it.