Federation Redirect

Document ID : KB000073228
Last Modified Date : 15/03/2018
Show Technical Document Details
Issue:
After configuring the OOTB Federation and having it work successfully, I had to update the Host Name from edidvwnssow01.xxxxx.net for the default Virtual Host to a new DNS entry sso-dev.sps.yyyyyy.net. IdP Federation worked successfully prior to this change.

After this update, when I perform an IdP initiated federation to the new URL: http://sso-dev.sps.yyyyyy.net/affwebservices/public/saml2sso?SPID=sso.saml20.sp.dev I receive a 302 redirect to the following URL where edidvwnssow01.xxxxx.net was the original URL that was used during the installation wizard of SPS and is the name of the server SPS is installed on:
http://edidvwnssow01.xxxxx.net/siteminderagent/redirectjsp/redirect.jsp?SPID=sso.saml20.sp.dev&SMPORTALURL=http%3A%2F%2Fsso-dev.sps.yyyyyy.net%2Faffwebservices%2Fpublic%2Fsaml2sso&SAMLTRANSACTIONID=2faa84a0-edaff9f5-9d3e5a5a-35ca3e0b-817e216d-94

This URL returns a Noodle Error:
Secure Proxy Server - Error Report Error Details
Request URI : /siteminderagent/redirectjsp/redirect.jsp
Error Type : SPS Exception
Error Code : VirtualHostNotFound
Message : Virtual host is not properly configured.
Cause:
The Authentication URL was not updated to reflect the new host name, thus when a user was redirected for authentication when reqeusting a federated application, they were redirected to an invalid host.
Resolution:
Authentication URL needs to be updated to reflect the host name change.