signer information does not match signer information of other classes in the same package - ASA Agent

Products

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

Issue/Introduction

 

We're starting an ASA Agent on WebLogic and this ones doesn't start properly and
reports error :

  ##<Nov 18, 2020 12:42:50,610 PM MEZ> <Error> <Security>
  <DEFR2WVWLG10> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <246006e6-df1d-439b-9c2d-4f13d93cd388-00000003>
  <1605699770610> <[severity-value: 8] [rid: 0] [partition-id: 0]
  [partition-name: DOMAIN] > <BEA-090870> <The realm "myrealm" failed to be loaded:

  weblogic.security.service.SecurityServiceException:
  java.lang.ExceptionInInitializerError.weblogic.security.service.SecurityServiceException:
  java.lang.ExceptionInInitializerError at
  weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)

  Caused by: java.lang.SecurityException: class  "org.bouncycastle.crypto.CryptoServicesRegistrar"'s signer information does not match signer information of other classes in the same package

How can we fix this ?

 

Environment

 

  ASA Agent 12.7 on WebLogic 12.2.1.4.0 (12c);

 

Cause

 

From the WebLogic logs we can see that the ASA Agent can't find a
config file :

weblogic_log.log :

  <Nov 20, 2020 4:43:13,351 PM MEZ> <Notice> <Security> <BEA-090946>
  <Security pre-initializing using security realm: myrealm>

  com.netegrity.siteminder.agentcommon.framework.b: Could not obtain smagent.properties from the classpath.

  Exception history:

   com.netegrity.siteminder.agentcommon.framework.b: Could not obtain smagent.properties from the classpath.

  [...]

  SiteMinder Identity Asserter initialization Failure.
  SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
  SLF4J: Defaulting to no-operation (NOP) logger implementation

From configuration, the SMASA_HOME environment variable hasn't been
configured properly, as it has set the string ASA_HOME instead of the
variable value %ASA_HOME% :

startWeblogic.bat

  set ASA_HOME=C:\Program Files\CA\smwlsasa
  set SMASA_HOME=ASA_HOME

ASA_HOME should have % characters such as :

  set SMASA_HOME=%ASA_HOME%

ref.:

  Enable and Disable the Authentication Provider

    set SMASA_CLASSPATH=%ASA_HOME%\conf;
    p.83

  https://ftpdocs.broadcom.com/cadocs/0/CA%20SiteMinder%20Agent%20for%20WebLogic%20r12%20SP2-ENU/Bookshelf_Files/PDF/SMWebLogicAgent_conf_enu.pdf

 

Resolution

 

- In startWeblogic.bat, set the following

  Change the line :

    set SMASA_HOME=ASA_HOME

  For 

    set SMASA_HOME=%ASA_HOME%  

  to solve the issue.