NOW-EDGE-KEYSTORE_MISSING_KEY NOW-EDGE-KEYSTORE_MISSING_KEY Severity High Root Cause The keystore doesn't contain the private key under the expected alias. (Edge uses several certificate key pairs; this one is used for SSL/TLS) Effect The startup of the Edge Proxy will end abnormally upon not being able to load the SSL/TLS private key Corrective Action Firstly, look up value of following properties in edgeencryption properties file: edgeencryption.proxy.https.keystore.path (keystore file location)edgeencryption.proxy.https.keystore.password (keystore password)edgeencryption.proxy.https.cert.alias (certificate alias) Secondly, ensure that the keystore file location corresponds to the value of the first property above. Thirdly, ensure that there is certificate and associated private key in the keystore stored under the alias (value of third property above), by executing the following: keytool -list -keystore /path/to/keystore_location -alias [alias]and when prompted with password, enter the value of the second property above. If no private key entry is found under that alias, you could list all private keys to see whether the certificate with associated key was persisted under a different alias by executing the following: keytool -list -keystore /path/to/keystore_location -v and when prompted with password, enter the value of the second property above in plain text. If the private key is not there, create a new SSL/TLS certificate and associated private key based on these instructions: https://www.servicenow.com/docs/bundle/yokohama-platform-security/page/administer/edge-encryption/task/t_SetUpSecureSSLConnection.html