Detected a problem with assertion: Unable to establish security of incoming assertion.

[Cantor, Scott]

On 12/1/14, 2:28 PM, "kripp" <kripp at compsych.com> wrote:

>We are the SP and are receiving a message from an IDP that is using IDP
>initiated POST binding.  I am seeing the following error in our logs "WARN
>Shibboleth.SSO.SAML2 [1]: detected a problem with assertion: Unable to
>establish security of incoming assertion."  This is the first time I have
>seen this problem and everything else seems to be getting processed
>correctly.  I've seen other posts indicate that it could have something to
>do with the clock on the IDP, but I'm not sure that is the case here.

Anything you read that says that is wrong. This is a signature issue, 
generally just a matter of incorrect metadata.

>  Below
>are the logs and decrypted Assertion with all personal information blocked
>out.  Please let me know if you can tell what the issue is.

You've omitted much of the log that will tell you what the problem is.

The assertion's not signed, so the response had better be, and there 
should be clear indications as to whether it was signed and validated.

-- Scott