forge VS certstrap

Maybe look into forge: https://github.com/digitalbazaar/forge

You might use the .env file, which sits inside a server, to store important passwords and keys to databases and APIs. Keeping it in text inside a .env is risky as it may get exposed if the server is compromised. To avoid this issue, one should use Encryption and Decryption. There are a couple of tools and libraries which offer similar functionality. You can try any of those, but we recommend using CryptoJS or Forge.

So setup a CA (I find certstrap simplifies this), load the CA cert into Mosquitto (cafile). Then you can issue any number of certificates that will allow clients to connect (you don't need to touch the broker config when adding new clients).

git clone https://github.com/square/certstrap cd certstrap git checkout v1.3.0 docker build -t squareup/certstrap . alias certstrap='docker run -i --rm -v $PWD:/out squareup/certstrap'

I like certstrap for this sort of thing, personally. I used to bugger about with OpenSSL but that’s far too real ale these days.

There are many ways to do this but my favorite is Certstrap.

Sounds like the issue is with your certificate itself, perhaps look at something which helps with local certificates management like https://github.com/square/certstrap

If you want to create your own CA, Certstrap by Square is really handy and simple to setup. I use this to generate valid certs for all my internal services (NAS, ESXI, etc).

Because OpenSSL is quite complex to use, we'll use certstrap for generation of certificates, install certstrap from here.