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

[Stephen Holland-Chang]

> 
>>   Does anyone know if there is a way we can debug the error and figure out which actual attribute is throwing the 
>> setHeader Failed error? 
> 
> Not mapping the attribute suspected is a simple way to prevent a header from being set for it, and given a separate installation and a trace it is eminently possible to reproduce a test of the processing of a message given other manipulation of security policy to bypass checks for freshness and other factors.

I have removed the attribute that is lengthy from the attribute-map.xml. Looking at the DEBUG it skips the attribute but still resolves the same error when the user attempts to login. Do I have to remove that attributes from the federationmetadata.xml as well so they dont send it at all?

>> Thats the only field that looks particularly distinctive.
> 
> Assuming the data is all ASCII/non-unusual, then I don't think there's any real doubt, but I would be concerned about there being multi-byte UTF-8 data involved too.

I do not see anything strange just looking at the xml in the log, do you have any recommendations for checking valid character encoding?


Thank you!