My Oracle Support Banner

Siebel AI Tomcat Server Fail to Initialize with Error " Alias name [null] does not identify a key entry" After Replacing Self-signed Certificates with CA Signed Certificates (Doc ID 2582830.1)

Last updated on OCTOBER 19, 2021

Applies to:

Siebel CRM - Version 19.7 and later
Information in this document applies to any platform.


Siebel is upgraded from IP15 to Siebel 19.7 with self signed certificates the application was working fine. As part of security policy, these self-signed certificates need to be replaced with signed certificates provided by root CA.

After importing CA provided certificates to JKS, AI is failing to come up.



21-Aug-2019 11:30:31.589 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["https-jsse-nio-9001"]
java.lang.IllegalArgumentException: Alias name [null] does not identify a key entry

The issue can be reproduced at will with the following steps:

1. Stop AI and import CA provided certificate to JKS
2. Start AI service.

3. AI failed to start




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.