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 MARCH 27, 2024

Applies to:

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


Unable to login to SMC, or AI failed to start on HTTPS port, or after replacing/renewal of certificates Siebel is not working. The following can be found:



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


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.


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.