Access Gateway's Federation Gateway not Using Custom ACO

Products

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

Issue/Introduction

Customer has configured separate, custom ACOs (Agent Configuration Objects) for each Virtual Host defined, but when processing federation requests, the default agent's ACO seems to be invoked.

 

Environment

Release : ALL

Component : SITEMINDER SECURE PROXY SERVER

Cause

Customer was seeing default agent invoked in the Affwebserv.log.  This is expected by default as the Affwebservices application is served locally from Tomcat and doesn't leverage the Virtual Host configuration.  

Resolution

As a localapp in Access Gateway/Tomcat, Affwebservices gets it's configuration from properties files rather than the Virtual Host configuration. Edit the <secure_proxy_home>/Tomcat/webapps/affwebservices/WEB-INF/classes/Affwebservices.properties file to adjust the location of WebAgent.conf and thus control which ACO is used by Affwebservices.