Yet another Idp error after SP upgrade
Peter Schober
peter.schober at univie.ac.at
Sun Aug 11 18:07:23 EDT 2013
* Mike Flynn <shibbolethlynda at yahoo.com> [2013-08-11 23:02]:
> Error from identity provider:
> Status: urn:oasis:names:tc:SAML:2.0:status:Requester
> Message: Invalid signature
* Nate Klingenstein <ndk at internet2.edu> [2013-08-11 23:08]:
> Make sure they're signing assertions with the same key that is in
> their metadata as loaded by you. The decrypted assertion should
> contain the key, making it easy for you to check that this is the
> issue.
>From the above error I'd say the IdP failed to verify the signed
authnRequest from the SP (status requester, and no asserion from the
IdP which could be encrypted to signed), so either the SP is using the
wrong credential for signing or the metadata the IdP has for this SP
is wrong.
Unless the IdP actually requires authnRequests to be signed you could
try not signing, for a start.
-peter
More information about the users
mailing list