Description

Currently, certificates musst start with -----BEGIN CERTIFICATE-----\n. When the certificate file was created on a windows system and not converted (e.g., with the dos2unix command line utility), the DSF FHIR Server / DSF BPE will not accept it.

Taking a first look at the certificate file does not really help, because cat/less/nano don't show the file encoding by default.

Effected DSF Version

<= 1.7.0

Expected Behavior

You can use both \nand \r\n to respresent new lines in a certificate / private key file.