Incoming binding urn:oasis:names:tc:SAML:2.0:bindings:SOAP is not enabled for (SP) :::

[Cantor, Scott]

On 11/26/17, 3:38 PM, "users on behalf of Tom Scavo" <users-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:

> This is great news. It means an SP deployment can choose to support
> SAML2 on the front channel only. No signing certificate needed in SP
> metadata.

There's nothing stopping that now, and if you need a key for encryption, then there's no advantage to omitting it for signing.

-- Scott