SiteMinder admin ui start up errors

Products

SITEMINDER CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On Agents (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder)

Issue/Introduction

12.8sp6 and 12.8sp6a admin ui start up with following errors out of box.

Admin ui itself works fine.

Server.log:

2023-02-26 06:07:46,167 ERROR [stderr] (MSC service thread 1-4) ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

...

2023-02-26 06java.lang.NullPointerException Product=Policy Server,Platform=Windows version 6.2 (Build 9200),Version=12.8,Update=06.00,Label=2649,Crypto=128,UTC=1677411257,TZ=5] server.logs:08:23,291 ERROR [ims.tmt.persistence] (ServerService Thread Pool -- 458) Data migration failed: null

Environment

SiteMinder Admin UI: 12.8sp6 and 12.8sp6a

OS Platform: ALL

Cause

These two errors are benign and cosmetic, and will not impact functionality.

Resolution

The first error is documented under link below:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/release-notes/known-issues/known-issues-for-policy-server.html#concept.dita_c30a346faa0cc09c960740a3e1dc4b6289a43f27_serverlogContainsIncorrectErrorLogs

As it says "the error logs can be safely ignored as they do not impact the functionality of SiteMinder."

Possible work around solution:

Go to the <Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main

Take backup of the existing "module.xml".

Open the module.xml. Add the below highlighted entries and save it.

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.ca.iam.log4j2.core">
<resources>
<resource-root path="log4j-core-2.12.0.jar"/>
<resource-root path="log4j-api-2.12.0.jar"/>
<resource-root path="."/>
</resources>
</module>

Copy the log4j-api-2.12.0.jar from "<Admin-UI-Installed-Location>/adminui//standalone/deployments/iam_siteminder.ear/library" to the "<Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main" location.

Copy the log4j_jboss.properties from the location "<Admin-UI-Installed-Location>\adminui\standalone\deployments\iam_siteminder.ear\config\com\netegrity\config to the
"<Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main" location.

Rename it as "log4j2.properties".

Go to location <Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/idmutils\main.

Take backup of the existing "module.xml".

Open the module.xml. Remove/Comment out the below highlighted entry and save it.

The second error was deemed NOT critical after Broadcom engineering's review.

Additional Information

DE559604