You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/operations/v2.0.0-RC2/root-certificates.md
+56-18Lines changed: 56 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Default Root Certificates
2
+
title: Trusted Certificates
3
3
icon: safe
4
4
---
5
5
@@ -10,55 +10,82 @@ Please ensure that you are using an organization-validated certificate (OV). We
10
10
:::
11
11
12
12
## Extending or Replacing Trusted Certificate Authorities
13
-
X.509 certificates of default trusted CAs are stored as .pem files containing multiple certificates in the docker images and can be replaced by either using docker [bind mounts](https://docs.docker.com/engine/storage/bind-mounts) or configuring appropriate environment variables with different targets.
13
+
X.509 certificates of default trusted CAs are stored as individual .pem files containing one certificate each in the docker images and can be replaced by either using docker [bind mounts](https://docs.docker.com/engine/storage/bind-mounts) or configuring appropriate environment variables with different targets.
14
14
15
15
### FHIR Reverse Proxy
16
16
Defaults are configured for the list of issuing, intermediate and root CAs used for validating client certificates (Apache httpd mod_ssl configuration option [SSLCACertificateFile](https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslcacertificatefile)) as well as the CA Certificates for defining acceptable CA names (option [SSLCADNRequestFile](https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslcadnrequestfile)).
17
17
Use the following environment variable to configure non default .pem files or override the existing files using docker bind mounts:
**Note:** Default file location are relative to the docker image work directory `/usr/local/apache2`.
24
24
**Also Note:** Using non default .pem files for the environment variables above may require also modifying the default values of the environment variables [SSL_EXPECTED_CLIENT_S_DN_C_VALUES](fhir-reverse-proxy/configuration.html#ssl-expected-client-s-dn-c-values) and [SSL_EXPECTED_CLIENT_I_DN_CN_VALUES](fhir-reverse-proxy/configuration.html#ssl-expected-client-i-dn-cn-values).
25
25
26
26
### FHIR Server
27
27
Defaults are configured for the list of issuing, intermediate and root CAs used for validating client certificates as well as root CAs used for validating server certificates of remote DSF FHIR servers and the OIDC provider when using [OpenID Connect](fhir/oidc.html) for authenticating local users.
28
-
Use the following environment variable to configure non default .pem files or override the existing files using docker bind mounts:
28
+
29
+
**Note:** Default file location are relative to the docker image work directory `/opt/fhir`.
30
+
31
+
You can add an additional certificate authority (e.g., your hospital CA) for
32
+
33
+
- server certificates by creating a bind-mount of the CA file into the `/opt/fhir/ca/server_root_cas/` directory
34
+
- client certificates by creating bind-mounts of the intermediate CA files and their root CA file into the `/opt/fhir/ca/client_ca_chains/` directory.
35
+
36
+
See the [BPE Server configuration](#bpe-server) for an example.
37
+
38
+
If you can't override the default configuration with bind-mounts, you can use the following environment variables to configure non default .pem file directories or .pem file:
Defaults are configured for the list of issuing, intermediate and root CAs used for validating client certificates (Apache httpd mod_ssl configuration option [SSLCACertificateFile](https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslcacertificatefile)) as well as the CA Certificates for defining acceptable CA names (option [SSLCADNRequestFile](https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslcadnrequestfile)).
40
48
Use the following environment variable to configure non default .pem files or override the existing files using docker bind mounts:
**Note:** Default file location are relative to the docker image work directory `/usr/local/apache2`.
47
55
**Also Note:** Using non default .pem files for the environment variables above may require also modifying the default values of the environment variables [SSL_EXPECTED_CLIENT_S_DN_C_VALUES](bpe-reverse-proxy/configuration.html#ssl-expected-client-s-dn-c-values) and [SSL_EXPECTED_CLIENT_I_DN_CN_VALUES](bpe-reverse-proxy/configuration.html#ssl-expected-client-i-dn-cn-values).
48
56
49
57
### BPE Server
50
58
Defaults are configured for the list of issuing, intermediate and root CAs used for validating client certificates as well as root CAs used for validating server certificates of local and remote DSF FHIR servers, the local mail server (if configured and SMTP over TLS required) and the OIDC provider when using [OpenID Connect](fhir/oidc.html) for authenticating local users.
59
+
60
+
**Note:** Default file location are relative to the docker image work directory `/opt/bpe`.
61
+
62
+
You can add an additional certificate authority (e.g., your hospital CA) for
63
+
64
+
- server certificates by creating a bind-mount of the CA file into the `/opt/bpe/ca/server_root_cas/` directory
65
+
- client certificates by creating bind-mounts of the intermediate CA files and their root CA file into the `/opt/bpe/ca/client_ca_chains/` directory.
66
+
67
+
If you have an additional certificate authority (e.g., your hospital CA) as `hospital-root-ca.pem` in your `/opt/bpe/secrets` directory, you can add it by adding the following entry in your docker-compose.yml file:
## List of Default Trusted Certificate Authorities
64
91
If not mentioned explicitly, issuing CAs listed will sign X.509 certificates with [Extended Key Usage](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.12) entries `TLS WWW server authentication` and `TLS WWW client authentication`.
@@ -143,6 +170,15 @@ If not mentioned explicitly, issuing CAs listed will sign X.509 certificates wit
143
170
Info: https://crt.sh/?caid=713
144
171
X509 Certificate: https://crt.sh/?id=133227
145
172
Not after: Nov 5 08:35:58 2029 GMT
173
+
* Root CA: **D-TRUST BR Root CA 1 2020 (ECC)**, optionally crosssigned by D-TRUST Root Class 3 CA 2 2009 [server only]
174
+
Info: https://crt.sh/?caid=192951
175
+
X509 Certificate: https://crt.sh/?id=3699642382 and https://crt.sh/?id=19754747817
176
+
Not after: Feb 11 09:44:59 2035
177
+
* Root CA: **D-TRUST BR Root CA 2 2023 (RSA)**, optionally crosssigned by D-TRUST Root Class 3 CA 2 2009 [server only]
178
+
Info: https://crt.sh/?caid=266681
179
+
X509 Certificate: https://crt.sh/?id=9609658147 and https://crt.sh/?id=19754898942
180
+
Not after: May 9 08:56:30 2038 GMT
181
+
146
182
* Root CA: **USERTrust ECC Certification Authority**[will be removed in a future release, incl. derived CAs]
147
183
Info: https://crt.sh/?caid=1390
148
184
X509 Certificate: https://crt.sh/?id=2841410
@@ -192,3 +228,5 @@ If not mentioned explicitly, issuing CAs listed will sign X.509 certificates wit
0 commit comments