Unmarshalling Metadata + &

[Cantor, Scott]

On 10/9/12 12:19 PM, "Chuck Kimber" <chuck.kimber at usu.edu> wrote:
>
>We had a database problem recently and so did a service restart of our
>Shibb IdP to reset the database connection.  Upon restart (read no
>changes made) we suddenly have an error about unmarshalling metadata.  I
>couldn't see any clues as to which metadata was
> in dispute, so proceeded to comment them out in our relyingparty file.
>Finally the culprit was identified when the error went away and our IdP
>started up.

One way is just to make sure that all of them are "non-fail-fast" and then
you can see which ones load correctly and which don't.

>I roll through the error and see a message about the "cause" which seems
>to be a raw amperstand in the metadata xml.  This metadata previously
>worked and never had this problem and is static in our file - provided by
>vendor ServiceNow for their SP.  I open
> the file and inspect/search for ANY amperstands, so I can replace them,
>but there are NO amperstands in the xml anywhere, nor can I spot any
>rogue xml tags floating around - everything is open, closed, attributed
>and namespaced correctly.  What else or where
> else should I be searching to find the cause of this "Unable to
>unmarshall metadata" error?  There are no other hints, other than
>disabling this SP's metadata, that would indicate which xml file is the
>root cause...

I might speculate then that it's not actually the file you think.
Otherwise, not much doubt about the error.

-- Scott