Follow these steps:
This error usually means that the certificates used for SAML authentication have been changed on one or both systems, and the available metadata has not been updated to reflect the new certificates.
Possible errors in messages.txt:
SAML Assertion is signed; signature is invalid
1) Check if the provided IdP metadata is correct. For example, an element "<KeyDescriptor use="signing">" needs to be present and it needs to contain a certificate:
2) If using a metadata URL starting with login.microsoftonline.com, make sure to have the appid specific part at the end: https://login.microsoftonline.com/SO...ME_OTHER_VALUE
In Microsoft terms, this is called the "App Federation Metadata URL".
SAML Assertion is not signed, a signature is required
Change the flag for -SignAssertion= from true to false, which is true of all flags.
The HTML error page can be customized by placing a file named shibfailure.htm into the EZproxy docs directory.