Unable to encrypt assertion - saml tracer
Peter Schober
peter.schober at univie.ac.at
Fri Jan 17 10:12:17 EST 2014
* Vignesh, Vanna G. <vignesh at musc.edu> [2014-01-17 15:38]:
> This is the error in the idp.process log. " Could not resolve a key
> encryption credential for peer entity: https://xyz.SP.com"; " Unable
> to construct encrypter - Could not resolve key encryption
> credential"
> The SP doesn't have any certificate in the metadata.
Which is just what Scott said.
> But by default, IDP is signing all the assertions in the relying
> party. Is that the problem?
No. Signing happens with the IdP's key and will work fine.
Encryption needs the SP's public key, so you can't use encryption with
an SP that doesn't have a key.
So create a RelyingParty element (after the DefaultRelyingParty) in
your relying-party.xml and set encryptAssertions="never" for that
specific SP to disable encryption of data to this SP.
-peter
More information about the users
mailing list