We have two policy servers in the cluster (12.52) on Windows machines. There are around 300 applications pointing to these 2 Production policy servers. We have a monitor to test the siteminder funcitonality using the Siteminder API. Today the Siteminder API (using the bootstrap smhost.conf) on one policy server could not connect to the policy server.  It is verifed from the psmc and also from task manager that the policy server is running. When we try to load the smHost.conf file in the Sitmeinder test tool, it is throwing the error stating that the configurations could not loaded. we have tried to re-register the trusted host present in this SmHost.conf file thinking that the shared secret might have been corrupted. But the re-registration always fails even when we tried with the different trusted hostnames. During this issue, no logs were logged (30 minutes) in the smaccess.log file. The issue is resolved only after the policy server restart. There were no issues on the second policy server.

 

We want to know the root cause for this issue.


Source: New feed
{pubDate}

Leave a Reply

Your email address will not be published. Required fields are marked *