signer information does not match signer information of other classes in the same package - Policy Server

Products

• SITEMINDER
• CA Single Sign-On
• CA Single Sign On Federation (SiteMinder)

Issue/Introduction

Upgraded Policy Server and when doing SAML Federation users are getting HTTP 500 in the browser and following message appears in the smtracedefault.log

"com.test.abc" is a random string to replace the actual string is the log and not the actual message.

[09/25/2023][12:51:08.664][12:51:08][18238][140227687458560][SmAuthUser.cpp:785][ServerTrace][][][][][][][][][][][][][][][][][][][][class "com.test.abc"'s signer information does not match signer information of other classes in the same package][CustomSAML2Assertion: class "com.test.abc"'s signer information does not match signer information of other classes in the same package]

Environment

Release : 12.8.x

Cause

This happens when classes belonging to the same package are loaded from different JAR files.

 

Resolution

Sometimes changing the order of jar files in the JVMOptions.txt may resolve this but our recommendation is that the custom jar files must be APPENDED in the JVMOptions.txt as we don't want to introduce other conflicts that may cause siteminder basic features to stop working.

Please test throughly when taking this approach.

 

Best way is to have your developer identify which jar files are in conflict first (by checking the dependencies) and decide on the best option to resolve this(above option included).