getting same error

I do not as SSC is not my area of expertise; however, you mentioned "load balancer'. From the SSC docs:

Although Fortify supports the use of multiple LDAP servers, it does not support the use of multiple LDAP servers behind a load balancer, unless those servers are identical.

ebell  do you think it can issue with the decoding in SSC as Destination in SAML Message shows Destination="https://fortify-ssc-xyz/ssc/saml/SSO/alias/urn:ssc:saml"

and the error states the SAML message intended destination endpoint did not match recipient endpoint 

I'm not sure. My recommendation would be to open a ticket with support and let them review.

Hello,

We solved this by modifying the SSC WEB-INF file to redirect to https.

This happens because the tomcat is with load balancer and who solved the https was the balancer while the tomcat was in http.