000022736 - How to apply RSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1 hot fix

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000022736
Applies ToRSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1
BEA WebLogic 8.1
IssueHow to apply RSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1 hot fix
After applying RSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1 hot fix, WebLogic server fails to start up
The following Java exception is returned when attempting to start BEA WebLogic server:

<Mar 20, 2006 2:11:49 PM PST> <Emergency> <WebLogicServer> <BEA-000342> <Unable
to initialize the server: java.lang.NullPointerException>
The WebLogic Server did not start up properly.
        at com.rsa.cleartrust.weblogic.security.common.exclusion.ExclusionListHa
ndler.loadExclusions(Unknown Source)
        at com.rsa.cleartrust.weblogic.security.common.exclusion.ExclusionListHa
ndler.<init>(Unknown Source)
        at com.rsa.cleartrust.weblogic.security.common.exclusion.ExclusionListHa
ndler.getExclusionListHandler(Unknown Source)
        at com.rsa.cleartrust.weblogic.security.providers.authorization.ClearTru
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSe
        at weblogic.security.service.SecurityServiceManager.createSecurityProvid
        at weblogic.security.service.AuthorizationManager.initialize(Authorizati
        at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATZ(Se
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.initiali
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadReal
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.initiali
        at weblogic.security.service.SecurityServiceManagerDelegateImpl.initiali
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
        at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
        at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
        at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
        at weblogic.Server.main(Server.java:32)
Reason: java.lang.NullPointerException
CauseThe Readme file distributed with RSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1 hot fix neglected to list a parameter added in the hot fix that was required. This is corrected in later hot fix distributions beginning in
ResolutionTo correct this issue, add the following parameter in the General section of cleartrust_realm.properties, in addition to the parameter for cleartrust.agent.web_filter_protected_apps_list:

# Comma-separated list of resource types that you want to exclude
# from ClearTrust access control checks. This parameter is supported
# by both Active as well as Passive mode of ClearTrust server. This
# parameter may be very useful if want to exclude resources based
# on their type.
# The default entries for this list is the resources types that are
# not supported by ClearTrust.
# Example:
# cleartrust.agent.resource_type_exclusion_list=&lt;jms&gt;,&lt;jndi&gt;
# "&lt;wlp&gt;,&lt;webservices&gt;,&lt;com&gt;" is the default setting for this parameter
# since they are not supported by ClearTrust. In addition, these resources
# must be present if you intend to run ClearTrust servers in Passive
# mode and they are optional in Active mode.

WorkaroundApplied hot fix to RSA ClearTrust Agent 3.5.2 for BEA WebLogic 8.1 to a working installation of WebLogic Server
Legacy Article IDa30115