ASA Agent Configuration error "Failed to Create Agent Configuration"

book

Article ID: 37357

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) AXIOMATICS POLICY SERVER CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

Symptoms:

------------

 

ASA agent created returns an error during initialization.

 

Environment:

------------------------

ASA agent R12.SP1 CR01

Red Hat Linux 6.x

Policy Server R12.52 SP1 CR02

 

 

ASA agent.log

 

==============

 

[26 Jan 2016 16:58:31,154] [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [INFO] The SiteMinder Agent is initializing .. 

 

[26 Jan 2016 16:58:31,160] [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [INFO] SiteMinder Product Details: PRODUCT_VERSION=6.0, PRODUCT_NAME=SiteMinder Application Server Agent for WebLogic 9.2 , PRODUCT_UPDATE=None, PRODUCT_LABEL=216. 

 

[26 Jan 2016 16:58:31,164] [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [INFO] Administration Manager is trying to create configuration for the SiteMinder Agent 

 

[26 Jan 2016 16:58:31,172] [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [INFO] Creating agent connection using file : /usr/local/nete/smwls11asa/aaa/bbbdomain/cccserver/conf/WebAgent.conf 

 Weblogic (Adminout.log)

-----------------------

below is the log snippet from web logic side:Adminout.log

 

com.netegrity.siteminder.agentcommon.framework.i: Failed to create agent configuration for : /usr/local/nete/smwls11asa/aaa/bbbdomain/cccserver/conf/WebAgent.conf 

 

at com.netegrity.siteminder.agentcommon.framework.d.a(DashoA10*..) 

 

at com.netegrity.siteminder.weblogic.sspi.common.b.a(DashoA10*..) 

 

at com.netegrity.siteminder.weblogic.sspi.auth.SiteMinderIdentityA

 

 

Cause:

---------

1)This can happen when we have install the ASA for the first time and using improper

/ wrong Java.home path different from WebLogic JVM.

 

2)If the Java is upgraded from the working setup.

 

Resolution:

------------

Ensure the AssertionAuthResource is configured in the Agent configurationObject and Realm is created matching the AssertionAuthResource value defined.

Ensure that java_home path in the (Smreghost file) which is installed with ASA agent matches the WebLogic java path and unlimited JCE patch for the Java version being used for the WebLogic instance as recommended in the ASA agent documentation.

Ensure that all the Java in the WebLogic JVM are also patched with the JCE, this should resolve the problem.

Environment

Release:
Component: SMBEA