XML Parsing Error: prefix not bound to a namespace

Cantor, Scott cantor.2 at osu.edu
Thu May 7 02:01:42 UTC 2020

> We are trying to figure out what this means.

It means exactly what people have said. The XML you're looking at is not what the SP is actually consuming, or there's a hidden character in there corrupting it.

The SP won't back up a metadata file that's invalid to disk, so the only thing you can do is access the SP on-host and do a direct fetch of the URL it's being given to load. There is absolutely no chance that the shibmd prefix is declared in that XML, or if it seems to be, it's not *actually* declared and there's a hidden character in it somewhere.

-- Scott

More information about the users mailing list