Alvearie / alvearie-helm

repository for the helm chart source and package for Alvearie projects
https://artifacthub.io/packages/helm/linuxforhealth
Apache License 2.0
3 stars 5 forks source link

[FHIR] Support for non-default server certificates #5

Closed lmsurpre closed 2 years ago

lmsurpre commented 3 years ago

The ibmcom/ibm-fhir-server docker image ships with a default self-signed certificate. This is handy because our fhir-client ships with a default truststore that is configured to trust the server. However, for real usage, this certificate should be replaced as needed for the target env.

As an example, the bitnami postgres chart has the following settings:

tls.enabled Enable TLS traffic support false
tls.autoGenerated Generate automatically self-signed TLS certificates false
tls.preferServerCiphers Whether to use the server's TLS cipher preferences rather than the client's true
tls.certificatesSecret Name of an existing secret that contains the certificates ""
tls.certFilename Certificate filename ""
tls.certKeyFilename Certificate key filename ""
tls.certCAFilename CA Certificate filename ""
tls.crlFilename File containing a Certificate Revocation List ""

Liberty can auto-generate a TLS cert, so maybe it would be good to expose that?

michaelwschroeder commented 2 years ago

We will enable the user to pass in their own keystore and truststore files via Secrets. The following values will be added to the values.yaml file to specify the Secret names:

For the keystore Secret, it will be expected to contain the content of the keystore file, the filename, and the password. The expected Secret keys are as follows:

Key Value
fhirKeyStore The contents of the keystore file
fhirKeyStoreFilename The name of the keystore file
fhirKeyStorePassword The keystore password

If a keystore secret is not specified, the default keystore will be used.

michaelwschroeder commented 2 years ago

Small design update:

We will enable the user to pass in their own keystore and truststore files via Secrets. The following values will be added to the values.yaml file to specify the Secret names and file formats:

For the keystore Secret, it will be expected to contain the content of the keystore file and the password. The expected Secret keys are as follows:

Key Value
fhirKeyStore The contents of the keystore file
fhirKeyStorePassword The keystore password

If a keystore secret is not specified, the default keystore will be used.