TLSNotary server wont start without private-key-pem-path
defined even when its unused
#565
Labels
good first issue
Good for newcomers
notary server
Improvements or problems in the notary server reference implementation
I just set up a TLSNotary server here: https://tlsnotary.zervice.io/ and wrote a guide for others in the process, but I encountered a minor issue in the process that I think is a bug.
TLSNotary fails to start when any of
private-key-pem-path
,certificate-pem-path
, orwhitelist-csv-path
are missing fromconfig.yaml
, even when thetls
andauthorization
sections are disabled withenabled: false
.According to the (excellent) docs, those files should not be needed when those features are disabled:
Error Output
Steps to reproduce
Full steps to reproduce here: https://docs.monadical.com/s/UrN0j1lpu
docker-compose.yml
:./tlsnotary/config.yaml
:If I create empty files in those locations and uncomment those lines in
config.yaml
then it starts without issue.The text was updated successfully, but these errors were encountered: