ECP issue with current opensaml-soap-impl

[Kim, Allan]

At UCSD we've run into some unexpected behavior while testing ECP with IdP 3.3.0-SNAPSHOT. The latest opensaml-soap-impl has added content type validation for SOAP requests in HTTPSOAP11Decoder, and accepts only text/xml as a valid type. I'm sure this is technically correct for SOAP 1.1 - however various ECP reference client implementations have gotten away with using other content types in the past and now seem to fail validation. For example ShibHttpClient from https://github.com/DARIAH-DE/shib-http-client sends text/plain, and I think SwiftECP sends application/vnd.paos+xml.

Is it possible to turn either content type validation or SUPPORTED_MEDIA_TYPES into configurable options? This would allow IdP deployers to support slightly out-of-spec clients while allowing other OpenSAML users to enforce strict validation when desired.

Thanks!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20161107/490c8505/attachment.html>