Upgrade sets back the out of the box keystore.jks in CA SiteMinder Adminui

Products

• CA Single Sign On Agents (SiteMinder)

Issue/Introduction

In situations where access to the SiteMinder Admin UI is customized by adding to  the Wildfly keystore.jks keystore file a custom certificate, an upgrade of the AdminUI causes the customization to be lost

For instance, before upgrade the standalone-full.xml file contains the following reference to the customized keystore:

<keystore alias="<alias_here>" key-password="<password_here>" keystore-password="<password_here>" path="keyStore.jks" relative-to="jboss.server.config.dir"/>

whereas upon upgrade, the default configuration is back:

<keystore alias="<default_alias_here>" key-password="<default_password_here" keystore-password="<default_password_here>" path="keyStore.jks" relative-to="jboss.server.config.dir"/>

and the certificates therein correspond to the out of the box certificates, that is, the custom certificate goes missing

Environment

CA SiteMinder versions 12.9 and below

Cause

This is working as designed. Upgrade of the Administrative UI causes any customization to the keystore to be lost and any custom certificate must be reapplied

Resolution

The customization must be reallied according to the documentation (1)

Additionally it is recommended to open an enhancement (2) to request for customization of keystore to be kept during upgrade if so wished. 

Additional Information

1. (Optional) Obtain and Import a Trusted Certificate into the Administrative UI
2. Creating an Idea/Enhancement Request for SiteMinder