Error: Could not create an Agent Connection in ASA Agent WebSphere
search cancel

Error: Could not create an Agent Connection in ASA Agent WebSphere

book

Article ID: 260447

calendar_today

Updated On:

Products

CA Single Sign On Agents (SiteMinder) SITEMINDER

Issue/Introduction

 

Starting ASA Agent with WebSphere, Websphere reports the error:

  Could not create an Agent Connection

SystemErr.log:

[2/20/23 11:58:17:650 EET] 00000001 SystemErr     R SM_WSK_00003 - SMERROR: SM_WSK_00006 - Unable to create configuration from the administration manager: Failed to create agent configuration for : C:\CA\smwasasa\conf\AsaAgent-assertion.conf
[2/20/23 11:58:17:650 EET] 00000001 SystemErr     R SM_WSK_00001 - SMFATAL: SiteMinder TAI ASA initialization error: SM_WSK_00007 - Unable to create configuration setup from the policy server
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R com.netegrity.siteminder.asaframework.common.a: SM_WSK_00007 - Unable to create configuration setup from the policy server
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R     at com.netegrity.siteminder.asaframework.common.SmAgentHelper.<init>(Unknown Source)
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R     at com.netegrity.siteminder.websphere.auth.SmTrustAssociationInterceptor.initialize(Unknown Source)
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R     at com.ibm.ws.security.web.TrustAssociationManager.loadInterceptor(TrustAssociationManager.java:497)
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R Caused by: com.netegrity.siteminder.agentcommon.framework.b: Failed to create agent configuration for : C:\CA\smwasasa\conf\AsaAgent-assertion.conf
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R Caused by: com.netegrity.siteminder.agentcommon.framework.h: ConfigurationManager failed to create agent connection.
[2/20/23 11:58:17:665 EET] 00000001 SystemErr     R Caused by: com.netegrity.siteminder.agentcommon.utils.l: Could not create an Agent Connection

 

Environment

 

ASA Agent 12.8SP2 on WebSphere 9.0

 

Cause

 

ASA Agent wasn't using the right SmHost.conf file.

 

Resolution

 

Delete the existing SmHost.conf and re-register the ASA Agent with the Policy Server to fix this issue.