When I'm uploading a CA and the uploaded file doesn't satisfy requirements, I should get an error message describing that the file is invalid and ideally what is wrong with it.
Probably the key and/or intermediate cert are missing from the file, but the requirements of how exactly the CA file should look like are not documented.
Current Behavior
Trying to upload a CA shows a fraction of a stack trace and then renders the UI unusable. The response I extracted from the browser dev tools looks like this:
Create a local CA with mkcert: CAROOT=$(pwd) mkcert localhost. Upload the resulting rootCA.pem as CA in the preflight UI.
I debugged a bit and figured out that the server expects the private key to be present in the .pem file as well. So I added it. But then it turns out we are expecting the key in the older PKCS#1 format, while my key was in the newer PKCS#8. After converting and combining it with the cert like this:
Expected Behavior
When I'm uploading a CA and the uploaded file doesn't satisfy requirements, I should get an error message describing that the file is invalid and ideally what is wrong with it.
Probably the key and/or intermediate cert are missing from the file, but the requirements of how exactly the CA file should look like are not documented.
Current Behavior
Trying to upload a CA shows a fraction of a stack trace and then renders the UI unusable. The response I extracted from the browser dev tools looks like this:
Steps to Reproduce (for bugs)
Create a local CA with mkcert:
CAROOT=$(pwd) mkcert localhost
. Upload the resultingrootCA.pem
as CA in the preflight UI.I debugged a bit and figured out that the server expects the private key to be present in the
.pem
file as well. So I added it. But then it turns out we are expecting the key in the older PKCS#1 format, while my key was in the newer PKCS#8. After converting and combining it with the cert like this:I got past the first error but ended up getting the following new error:
Your Environment
graylog/graylog-datanode:5.2.0-beta.1-1
(docker image)