Using self-signed certificates¶
Open Zaak supports self-signed certificates in two ways:
Hosting Open Zaak using self-signed certificates - this is the classic route where your web server/ingress is configured appropriately
Consuming services hosted with self-signed certificates - this is what this guide is about.
Open Zaak communicates with external services such as Open Notificaties, Github and
the VNG Selectielijst service. It does this using
https - using http is insecure.
When Open Zaak makes these requests, the SSL certificates are varified for their validity - e.g. expired certificates or certificates signed by an unkonwn Certificate Authority (CA) will throw errors (as they should!).
When you’re using self-signed certificates, you are essentially using an unkonwn CA, and this breaks the functionality of Open Zaak.
Adding your own certificates or CA (root) certificate¶
Open Zaak supports adding extra, custom certificates to the provided CA bundle. You do
this by setting an environment variable
EXTRA_VERIFY_CERTS, which must be a
comma-separated list of paths to certificate files in PEM format.
An example of such a certificate is:
-----BEGIN CERTIFICATE----- MIIByDCCAW8CFBRCXMlcdJAPb8XkG4cYMNL+Ku17MAoGCCqGSM49BAMCMGcxCzAJ BgNVBAYTAk5MMRYwFAYDVQQIDA1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHDAlBbXN0 ZXJkYW0xEjAQBgNVBAoMCU9wZW4gWmFhazEYMBYGA1UEAwwPT3BlbiBaYWFrIFRl c3RzMB4XDTIxMDMxOTExMDYyM1oXDTI0MDMxODExMDYyM1owZzELMAkGA1UEBhMC TkwxFjAUBgNVBAgMDU5vb3JkLUhvbGxhbmQxEjAQBgNVBAcMCUFtc3RlcmRhbTES MBAGA1UECgwJT3BlbiBaYWFrMRgwFgYDVQQDDA9PcGVuIFphYWsgVGVzdHMwWTAT BgcqhkjOPQIBBggqhkjOPQMBBwNCAASzDq7C9atfN3uxoAGOCro8RfzWloVusDeO bwXztxUC/wBu4WgfRsYjg65eVzaJWQKvIKn5W9rGyuIAYbJZJtMZMAoGCCqGSM49 BAMCA0cAMEQCIHKCp4qVEzF3WgaL6jY4tf60HBThnQTaXC99P7TaIFhxAiASMBVV tmukm/NP8zSMrNpEGLnGIFa8uU/d8VwNNPFhtA== -----END CERTIFICATE-----
Typically you would do this by (bind) mounting a volume in the Open Zaak container containing these certificates, and then specify their paths in the container, for example:
docker run \ -it \ -v /etc/ssl/certs:/certs:ro \ -e EXTRA_VERIFY_CERTS=/certs/root1.crt,/certs/root2.crt open-zaak/open-zaak:latest
Of course, you will need to adapt this solution to your deployment method (Helm, Kubernetes, single-server…).