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

[Tom Scavo]

On Wed, Nov 22, 2017 at 8:08 AM, Pruvost, Christian (ELS-OXF)
<c.pruvost at elsevier.com> wrote:
>
> <md:AttributeAuthorityDescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
>                 <!--md:AttributeService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding" Location="https:// idp.domain:9443/idp/attrsvc.ssaml2"/-->
>                 <md:AttributeService Location="https://idp.domain:9443/idp/attrsvc.ssaml2" Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"/>
>                 <md:NameIDFormat>urn:mace:shibboleth:1.0:nameIdentifier</md:NameIDFormat>
>                 <md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</md:NameIDFormat>
> </md:AttributeAuthorityDescriptor>

That metadata fragment isn't very encouraging. There seems to be some
confusion about SAML1 support. In particular, I doubt this IdP
supports urn:mace:shibboleth:1.0:nameIdentifier for SAML2, but in any
case, did you check your logs to see exactly what your SP is sending
the IdP?

Tom