Describe the bug
I am trying to use the extension with a scality server (that uses the same protocols as aws s3) which uses a custom ssl certificate. Jupyterlab is running inside of a docker container. I added the custom .pem entry to the file /opt/conda/ssl/cert.pem. I am able to make a request with curl to the scality server within the docker container without any ssl error (there was an error before adding the .pem entry). But when trying to login within the s3-browser extension, I am getting this error
SSL validation failed for https://scality-server-url [...] certificate verify failed: unable to get loca lissuer certiicate (_ssl.c:1006)
This probably means that the extension uses another certificate store than the one of conda (there is only one conda env, base)
Desktop (please complete the following information):
Describe the bug I am trying to use the extension with a scality server (that uses the same protocols as aws s3) which uses a custom ssl certificate. Jupyterlab is running inside of a docker container. I added the custom .pem entry to the file
/opt/conda/ssl/cert.pem. I am able to make a request with curl to the scality server within the docker container without any ssl error (there was an error before adding the .pem entry). But when trying to login within the s3-browser extension, I am getting this errorThis probably means that the extension uses another certificate store than the one of conda (there is only one conda env, base)
Desktop (please complete the following information):