Tech Tip : CA Single Sign-On : Federation web Services(FWS) Failing to initialize

Document created by Osarobo_Idehen Employee on Sep 8, 2017
Version 1Show Document
  • View in full screen mode

Issue:


We are observing an issue where Federation Web Services (FWS) is failing to initialize with the below error in the affwebservices.log.

The environment variables are sourced correctly and the path to the waop bin directory is the first entry in the LD_LIBRARY_PATH.

We also restarted the Application Server, but the issue persists. How can we resolve this issue?

affwebservices.log:

[2120/2540300032][Thu Jul 27 2017 15:57:55][agentcommon][INFO][sm-FedClient-00010] sm-FedClient-00010 (The SiteMinder Agent is initializing ..)

[2120/2540300032][Thu Jul 27 2017 15:57:55][agentcommon][INFO][sm-FedClient-00010] sm-FedClient-00010 (SiteMinder Product Details: PRODUCT_UPDATE=0000 , PRODUCT_NAME=Federation Web Services, PRODUCT_LABEL=142, PRODUCT_VERSION=12.52.)

[2120/2540300032][Thu Jul 27 2017 15:57:55][agentcommon][INFO][sm-FedClient-00010] sm-FedClient-00010 (Administration Manager is trying to create configuration for the SiteMinder Agent)

[2120/2540300032][Thu Jul 27 2017 15:57:55][agentcommon][INFO][sm-FedClient-00010] sm-FedClient-00010 (Creating agent connection using file : /opt/CA/webagent_optionpack/config/WebAgent.conf)

[2120/2540300032][Thu Jul 27 2017 15:57:59][FWSAdministrationManager.java][ERROR][sm-FedClient-00050] sm-FedClient-00050 (Failed to create agent configuration for : /opt/CA/webagent_optionpack/config/WebAgent.conf)

[2120/2540300032][Thu Jul 27 2017 15:57:59][FWSAdministrationManager.java][ERROR][sm-FedClient-00060] sm-FedClient-00060 ()

 

[2120/2540300032][Thu Jul 27 2017 15:57:59][ManageNameIDService.java][INFO][sm-FedClient-01520] sm-FedClient-01520 (NameID Management)

 


Environment:

 

Policy Server 12.52.x on Windows 2008R2 WA/WAOP 12.52.x on RedHat 6 64bits

 


Cause:


FWS fails to initialize because the shared secret from the SmHost.conf is corrupted and Policy Server doesn't recognize it.

 


Resolution:


Apply below steps to resolve the issue:

1) Delete trustedHost within AdminUI

2) Re-register the agent back with the Policy server

3) Restart services

 

 

KD : TEC1412927

Attachments

    Outcomes