SP Error: Message was signed, but signature could not be verified

[Jeff Gehly]

Some updates to this.  I did take a look a the logs and it's interesting. 
The signing is happening on the response object.  The fun part is that it
will accept the signature some of the time but rejects it others.

Near as I can tell, the rejection happens when the load balancer sends the
whole request through server B instead of server A.  I would say that it's
likely the servers have different certificates because they reside on
separate physical hardware and are configured to run independent of each
other.

Since this seems to be the case, how do I configure Shibboleth to trust both
servers so that it doesn't think there's a spoof happening?



--
View this message in context: http://shibboleth.1660669.n2.nabble.com/SP-Error-Message-was-signed-but-signature-could-not-be-verified-tp7587180p7587269.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.