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

Rod Widdowson rdw at steadingsoftware.com
Wed Nov 22 08:47:42 EST 2017


I'm a bit confused here 

> . We have a working SAML2 Service Provider working hundreds of IDP

Do you mean a Shibboleth SP?  

> 
> <S11:Envelope xmlns:S11="http://schemas.xmlsoap.org/soap/envelope/"><S11:Body>
> <S11:Fault><faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</faultcode>
> <faultstring>Incoming binding urn:oasis:names:tc:SAML:2.0:bindings:SOAP is not enabled for (SP) :::
https://sdauth.sciencedirect.com/</faultstring></S11:Fault></S11:Body></S11:Envelope>

Well that’s coming from the IdP.  And AFAICS in the code, no (current) Shibboleth IdP would generate that string.  So I would guess
that it is incumbent on the people running the IdP to fix something.  It is also interesting that they chose to not push the
encrypted attributes to you.

/R



More information about the users mailing list