search cancel

The smreghost utility fails to overwrite existing trusted hosts and gives error "Registration failed (Unable to create trusted host.)".


Article ID: 50819


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On



The overwrite flag [-o] in the smreghost tool which is supposed to overwrite an already existent object does not work.

The smreghost command is like:

smreghost -i <policy_server> -u admin -p passwd -hc hostconfig -hn

<already_existent> -f /var/tmp/SmHost.conf -o

The response is: "Registration failed (Unable to create trusted host.)"


smreghost could not overwrite existing trusted hosts in 6.0 SP6 & 6.0 SP6 CR1 releases.

In 6.0 Sp6, the mechanism to overwrite register hosts was modified to look for existing trusted hosts only in secondary cache and delete the same before saving the new trusted host object again. If the secondary cache is not built by this time, this deletion would not remove the actual trusted host and when we try to save it again the object and we would fail.

The fix is implemented in 6.0 SP6 CR2 release will fetch the object directly from the primary cache/provider if it is not found in cache.


Component: SMPLC