KB Article #189780
How to add a custom certAlias in a cloud environment starting with AFAH 3.0 U8
Problem
Following the upgrade to AFAH 3.0.8.0 upgrade, some errors might be encountered, most likely linked to the addition of the keyAlias feature in FAH 3.0 U8:
19-Feb-2025 10:20:04.210 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector["https-jsse-nio-8443"]]
org.apache.catalina.LifecycleException: Protocol handler initialization failed
at (...)
Caused by: java.lang.IllegalArgumentException: Alias name [${TomcatCertAlias}] does not identify a key entryResolution
The installation or upgrade to U8 in cloud should use the helm chart version 3.16.11
In the helm values there is a default value for this variable:

To add the TomcatCertAlias to the Tomcat environment, you have several options. If you have a custom alias when creating the keystore file, you should use that value instead of "sample".
Option 1: Using setenv.sh (Recommended)
- Add to setenv.sh
export TomcatCertAlias="sample"
Option 2: Using Helm Values
In your values.yaml:
global:
certAlias: "sample"Then, in the deployments templates:
env:
- name: TomcatCertAlias
value: {{ .Values.global.certAlias }}