Hi Team,
I have a question, please give me some advice.
[Environment]
OS Windows Server 2016
SiteMinder 12.8 SP07
We changed the OS hostname and IP addresses on a total of four servers that make up "Site Minder" and also changed the SiteMinder settings at the same time.
After the change, when accessing "WAM UI" with the new hostname (FQDN), we are being redirected to the old hostname (FQDN), so we would like to change the settings so that this does not happen.
*Currently, as a temporary workaround, we have set up a definition in the OS hosts file that returns the new IP address with the old hostname (FQDN), and we are able to access "WAM UI".
[Inquiry Content]
1. Regarding the deletion of "TrustedHost: Localhost_x" when reconfiguring the "WAM UI"
- I checked your knowledge base article, "Change the hostname in SiteMinder Administrative UI,"
and found that "Name: Localhost_0" through "Name: Localhost_7" existed on the actual device.
I assume the above settings are affecting this, but would it be okay to delete only "Name: Localhost_0",
or delete all of "Name: Localhost_0" through "Name: Localhost_7" and then reconfigure?
Also, if I make the above setting changes, will the SSO function be affected?
2 Are there any settings other than TrustedHost that would improve the redirect behavior?
3. Regarding the impact on services when the "WAM UI" access URL is still the old hostname (FQDN)
- Will the SSO function be affected if it is currently redirected to the old hostname (FQDN)?