-
Hello, I was able to successfully configure Teleport and MinIO as a backend for session recording following this procedure. Now I want to switch to https. I followed this procedure to setup MinIO for https using a self-signed certificate with the minio utility certgen. This step was successful: I checked it by executing Then I updated the teleport configuration file
to
Unfortunately looking at the official teleport documentation and searching the Internet I could not find any instruction on how to set in teleport the CA certificate of MinIO (in this case the self-signed certificate). Indeed if restart teleport, I get the following records in the teleport log:
And If I try to play any session recorded before the switch to https for MinIO, I get an errror with the same meaning:
Where do I have to save the MinIO self-signed certificate and where can I tell teleport to look for it? Thanks in advance NOTE: in my current setup both teleport and MinIO run on the same host, so now using http is not a problem, but I would like to run the two product on two different hosts, then the need to use https. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Teleport will use the system trust store, so if you trust the Minio CA at the system level it should work fine. This process varies from system to system, but for Linux it usually involves putting the file under |
Beta Was this translation helpful? Give feedback.
Thanks a lot for the reply.
In my Ubuntu 24.04 installation, after copying the MinIO self-signed certificate to
/usr/share/ca-certificates/mozilla
, I had to use the commanddpkg-reconfigure ca-certificates
following this procedure (see the first answer), to update the system trust store with the MinIO self-signed certificate.Then when restarting teleport, the error on S3 initialization disappeared and the playing of the sessions previously recorded worked fine.