Look some more on the web then (sorry for the tongue in cheek answer. I know it’s tough to scour the web for something like this)
I’d argue this isn’t something specific to Metabase - but more related to that you need to add your self signed cert as a trusted cert to the javakeystore on the machine running Metabase, then make sure it’s referenced correctly when Metabase is started.
Here’s a possible starting point (with it’s StackOverflow link):
The way I’d possibly go about it (if you can’t get it running with Metabase right away) would be to test certificate setup with e.g a simple “Hello World” java code snippet/command line tool using or building on the java Mongo client libs (guess it’s this. https://mongodb.github.io/mongo-java-driver/). When you have that working then getting it working with Metabase shouldn’t be as hard.
Sorry, that’s all I can offer as I haven’t been through setting up a client with Mongo and self-signed … only lots of other things patterned around the same.
Hi @GillesCP, could you help me telling where did you find the ROOTCA.pem ? As we have a self-signed certificate? I’ve tried to create the .pem like this link, when I try the commands as you wrote above I’ve got or: "java.io.FileNotFoundException: /usr/lib/jvm/java-1.8-openjdk/jre/jre/lib/security/cacerts (Is a directory)
" or “java.lang.Exception: Input not an X.509 certificate”