Hi
FMS seems to accept an intermediate certificate containing only and directly the root CA. This is possible e.g. when MS AD issues certificates for internal use.
I wonder if Otto Deploy accepts this likewise. The server connection error Error: unable to verify the first certificate still occurs in such a configuration while FMS accepts the certificate files.
Can somebody say something about this? What exactly needs to be provided in a single tier PKI in a internal network with Windows hosts?
Yes, the certificate config is required if the certificate is from a non-standard CA. OttoFMS is using Node.js which uses a built in CA list, so CAs are not loaded from the host (unless you’re running on Mac). For Linux and windows you would need the setup you described and described in the custom cert docs.