Has anyone seen an error like this before right after a SAML Post to the
IdP:

Warning: Invalid resource key: Signature length not correct: got 128 but
was expecting 256. No prefix!
Warning: Invalid resource key: Signature length not correct: got 128 but
was expecting 256. No prefix!
<amLogEntry> 2014-01-17T15:32:42Z INFO NIDS IDFF: AM#500106006:
AMDEVICEID#EDAAAF41FA680100: Validation failure on message from
payreview.
ehr.com : Signature length not correct: got 128 but was expecting 256
</amLogEntry>


I have an app that worked fine under AM 3.1, doing SAML using the
Artifact method (so the SP directly posts a request to the IdP). Just
tried switching to a new 4.0 IdP and I get this error. There is a new
cert being used to generate the signature now (updated in the metadata),
but this happens no matter what I put in there. I don't think the
signature is ever even attempted to be validated.

Thanks.

Matt


--
matt
------------------------------------------------------------------------
matt's Profile: https://forums.netiq.com/member.php?userid=183
View this thread: https://forums.netiq.com/showthread.php?t=49728