Encryption configuration issue

[Raymond DeCampo]

Rod,

I did try your suggestion as well, changing the KeyDescriptor use to
"encryption" however when I did that I ended up with the following
error on the mellon side:

Error processing authn response. Lasso error: [-427] When looking for
an assertion we did not found it., SAML Response:
StatusCode1="urn:oasis:names:tc:SAML:2.0:status:Success",
StatusCode2="(null)", StatusMessage="(null)", referer:
https://samldev.promergent.com:8443/idp/profile/SAML2/Redirect/SSO?execution=e2s2

But since I was able to use samltest.id as the SP and it has
encryption configured, I'm thinking this is probably an issue with my
use of mellon.

Thanks,
Ray

On Wed, Jul 29, 2020 at 12:01 PM Rod Widdowson <rdw at steadingsoftware.com> wrote:
>
> > 2020-07-29 11:35:57,343 - 10.42.0.200 - WARN
> > [org.opensaml.xmlsec.impl.BasicEncryptionParametersResolver:234] -
> > Validation failure: Failed to resolve both a data and a key encryption
> > credential
>
>
> >     <KeyDescriptor use="signing">
>
> But no <KeyDescriptor use="encryption"/> ?
>
>
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net