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

Stephen Holland-Chang stephen at
Tue Jan 26 07:33:15 UTC 2021

Thanks Rod

> On Jan 22, 2021, at 7:35 AM, Rod Widdowson <rdw at> wrote:
>> Then there really isn't any doubt, nor any doubt that IIS is so broken that it apparently doesn't honor the setting you're trying to
>> change, or has some inherent limitation that overrides the setting.
> I have the very vaguest of memories that IIS can get a bit upset if you try to set a header which has some sort of sematic meaning (and in particular REMOTE_USER rings bells).  Are there any names like that?

 I do not have anything that mentioned REMOTE_USER. This configuration worked fine in SP 2 and since we moved to SP 3 this error starting happening. 

> If you add a case to JIRA so I don't forget, it would not be hard to add better logging in the future.
> As for debugging it - I am assuming that this is a production machine?  If so then I have no ideas.

Yes it is a production machine. I just wish that I could see what’s specifically throwing the error instead of just the xmltooling::IOException which the user gets. So let me get this right, the IDP posts back the SAML2 response , Shibboleth SP gets it, maps all the values which I can see in the shibd.log and it redirects them to my application URL passing the header data, so between passing the data through to IIS header and my page loading it errors with the xmltooling:IOException error.

This is Shibboleth catching the error correct?

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

More information about the users mailing list