Troubleshooting the "Unable to decode" (IdP 3.3)

[O'Dowd, Josh]

We are getting a regular stream of bad requests, from a specific IP subnet range, which are logging the "Unable to decode" and "Cannot Unmarshall XML" errors.  I have tried tuning up the log level for opensaml and for messages, but I can only get the IP address.  It appears 'messages' logger only debugs out valid messages and not invalid ones; I assume for good reason.

Is there any known way to get a look at these incoming SAML requests without knowing what entity is, only that the subnet is registered to Facebook?

Thanks for the help.

Josh O'Dowd
Software Systems Engineer / Identity Access Management
Central IT, University of Montana

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170825/d73defa8/attachment.html>