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

Cantor, Scott cantor.2 at
Tue Jan 26 13:28:12 UTC 2021

On 1/26/21, 2:27 AM, "users on behalf of Stephen Holland-Chang" <users-bounces at on behalf of stephen at> wrote:

>    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?

No. The only obvious thing to do is keep ruling out attributes one at a time and file a bug so we get the header name logged. If it had ever happened in 20 years it would be logged already but the error check is pro forma, there's nothing documented by MS that would cause it to fail.

You can also file a bug and attach a trace of the response so somebody can reproduce the issue, but being that you're not a member, that's not going to happen outside of the ordinary course of development, which means many months as there are no SP releases planned.

-- Scott

More information about the users mailing list