I have a newly created certificate that I want to use to secure browser-to-kibana communication. Our previous cert was sha1 and the new one is sha2 and it is issued by a different certificate authority. After editing the kibana.yml and restarting kibana I get an error saying the certificate is not trusted and offering the "I understand the risk" option of adding an exception, something I don't want to have to do.
A couple things cross my mind:
- is kibana 4.6.4 capable of using a sha2 cert?
- does my truststore have my new certificate authority? I suspect not but I don't know what truststore is being used. How do I determine which truststore I need to upgrade?
Craig