"SAML response signature is not valid. "

[Cantor, Scott]

On 2/28/17, 8:53 PM, "users on behalf of IAM David Bantz" <users-bounces at shibboleth.net on behalf of dabantz at alaska.edu> wrote:

> It is a good thought, as the problem started around the same time as AWS S3 issue today;
> but it persists now hours after AWS restoration of services.

It seems plausible that they lost configuration and reverted to some default state perhaps, and don't know what their system was actually doing originally. For example perhaps it defaults to requiring SHA-1 and they hacked it to accept SHA-2 and now don't remember what they did.

Could be literally anything, but you can't figure it out for them.

-- Scott