Service failed to start "Alias name automation does not identify a key entry"

Products

• CA Process Automation Base

Issue/Introduction

After configuring the custom certificate, service failed to start with below error messages in c2ow.log file:
-------------------
INFO   | jvm 1    | 2022/07/07 08:15:40 | 2022-07-07 08:15:40,620 ERROR [org.apache.coyote.http11.Http11Protocol] Error initializing endpoint
INFO   | jvm 1    | 2022/07/07 08:15:40 | java.io.IOException: Alias name automation does not identify a key entry

INFO   | jvm 1    | 2022/07/07 08:15:40 | 2022-07-07 08:15:40,622 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=WebServer state=Create
INFO   | jvm 1    | 2022/07/07 08:15:40 | LifecycleException:  Protocol handler initialization failed: java.io.IOException: Alias name automation does not identify a key entry

INFO   | jvm 1    | 2022/07/07 08:15:51 | DEPLOYMENTS IN ERROR:
INFO   | jvm 1    | 2022/07/07 08:15:51 |   Deployment "WebServer" is in error due to the following reason(s): LifecycleException:  Protocol handler initialization failed: java.io.IOException: Alias name automation does not identify a key entry

INFO   | jvm 1    | 2022/07/07 08:24:37 | Shutdown complete
INFO   | jvm 1    | 2022/07/07 08:24:37 | Halting VM
STATUS | wrapper  | 2022/07/07 08:24:38 | <-- Wrapper Stopped
-------------------

Environment

Release : 4.3.X

Component : Process Automation

Cause

The parameter "itpam.web.keystorealias" in OasisConfig.properties file is not having the same value (alias name) that is configured with the Keystore.

Resolution

• Run below command from JDK bin directory to check the contents of Keystore:
  keytool -v -list -keystore <path to keystore file>
• Note the alias name from the output.
• Set the same alias name to "itpam.web.keystorealias" parameter in OasisConfig.properties file and restart the Orchestrator service.

Additional Information

Click here for more information on using third-party certificate