WebAgent mis-configures Policy Server ports in SmHost.conf if Policy Server is running on custom ports while doing Host Registration

Article Id: 51166
Status: Published
Updated On: 14-02-2018 07:01
Legacy Id: TEC533024
Products:
CA Single Sign On Secure Proxy Server (SiteMinder) , AXIOMATICS POLICY SERVER , CA Single Sign On SOA Security Manager (SiteMinder) , CA Single Sign-On , CA Single Sign-On
Issue/Introduction:

Description:

During WebAgent configuration -> in the step of Policy Server Registration (SmHost.conf file generation); If the Policy servers are running on custom port, and more than one policy server needs to be configured then WebAgent adds incorrect entries in the SmHost.conf.

For E.g.-

When multiple policy servers are configured with custom ports (or same policy server configured twice with custom port) then WebAgent appends additional port in the SmHost.conf file as shown below:-

  • Configure 2 policy servers to run on custom authentication port for e.g. 4441

  • Configure a WebAgent and do the host registration

  • Enter the IP address of both policy servers and the custom port for e.g.

    192.168.10.1:4441
    192.168.10.2:4441

  • Complete the registration and check the SmHost.conf.

  • WebAgent adds following entries for policy server in the SmHost.conf:

    192.168.10.1,4441,4441,4441
    192.168.10.2:4441,4441,4441,4441

We can see that the second line is not okay, as WebAgent has added an additional port for the second Policy server entry.

Because of this; if you stop the first policy server (192.168.10.1:4441), the WebAgent cannot contact the second policy server 192.168.10.2 that is the second in the bootstrap of the SmHost.conf and can't retrieve its HCO, so doesn't start.

Note: This issue does not occur if there is only have one policy server to be configured.

This issue exits on 6QMR5 WebAgent as well as with R12-SP2 WebAgent.

Solution:

This issue has been fixed in WebAgent Version R12-SP3.Now WebAgent correctly configures the policy server and their ports during WebAgent configuration.

For E.g. - After the fix

Case-1: Configure 2 policy servers (192.168.10.1, 192.168.10.2) to run on custom authentication port for e.g. 4441 and then perform WebAgent configuration for host registration.

Result: host registration will be successful and the entries in the SmHost.conf should be like:

192.168.10.1,4441,4441,4441
192.168.10.2:4441,4441,4441

Case-2: configure 1st PS using custom port and 2nd PS using default port. Do the host registration.

Result: host registration will be successful and the entries in the SmHost.conf will be:
192.168.10.1,4441,4441,4441
192.168.10.2:44441,44442,44443

Case-3: Configure 1st PS using default port and 2nd PS using custom port. Do the host registration.

Result: host registration will be successful and the entries in the SmHost.conf will be:

192.168.10.1,44441,44442,44443
192.168.10.2:4441,4441,4441

Case-4: Now configure both PS's using default ports.

Result: host registration is successful and the entries in the SmHost.conf will be:

192.168.10.1,44441,44442,44443
192.168.10.2:44441,44442,44443

Environment:

Release:
Component: SMAPC