Mercurial > libervia-backend

view docker/backend-dev-e2e/certificates/README @ 3634:3c7a64d6f49f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
bridge: bridge can now be set using environment variable: The `LIBERVIA_BRIDGE_NAME` environment variable can now be used to specify the bridge to use. If set and different from empty string, the environment has precedence over config file value. For `pb` bridge, the following environment variable can also be used: - LIBERVIA_BRIDGE_PB_CONNECTION_TYPE - LIBERVIA_BRIDGE_PB_HOST - LIBERVIA_BRIDGE_PB_PORT
author Goffi <goffi@goffi.org>
date Sat, 28 Aug 2021 15:26:02 +0200
parents 73e04040d577
children
line wrap: on
line source

Those certificates are used to activate TLS for end-2-end testing (to be as
close as possible as production environment), they are used in other containers
needing TLS certificates (notably Prosody).

To generate them, minica has been used. Minica can be found at https://github.com/jsha/minica.

The following commands have been used:

$ minica --domains "server1.test,*.server1.test,server2.test,server3.test,libervia-backend.test,libervia-web.test"
$ chmod 0644 minica.pem server1.test/cert.pem && chmod 0640 server1.test/key.pem

Note that certificates are valid for 2 years and 30 days, so they must be renewed after this delay.