Shibboleth SP3 Problem: xmltooling::IOException setHeader (Header) failed: -2147024809

Stephen Holland-Chang stephen at
Fri Jan 15 00:28:42 UTC 2021

Thanks for helping me understand the logger better. That worked and I found out that the decrypted attributes being passed are prepended with a value which includes a backslash. 

For example:

Could the \ be causing problems with Shibboleth setting the data into the request header? If so, are there any options for escaping that in Shibboleth?

Thanks for the help!


> On Jan 14, 2021, at 12:09 PM, Cantor, Scott <cantor.2 at> wrote:
> On 1/14/21, 3:06 PM, "users on behalf of Stephen Holland-Chang" <users-bounces at on behalf of stephen at> wrote:
>>   Ive looked at the log configuration guide for Shibboleth SP 3 but still cannot see anywhere in logs to show me which
>> SAML2 data that keeps failing. 
> The part that tells you to use shibd.log for anything important, which is configured by shibd.logger.
> However I would say the native.logger file is long broken, most of the categories in it are only in the other log file so they're misleading by including them there.
> -- Scott
> -- 
> For Consortium Member technical support, see
> To unsubscribe from this list send an email to users-unsubscribe at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list