Fwd: [InC-Admin] bug in Incommon-metadata.xml

[Tom Scavo]

At this moment, there is a "spurious character" in InCommon metadata
[1] that reportedly is "breaking embedded discovery." Unfortunately, I
don't have any more information about the breakage since the report
was received third hand. That's why I'm reporting it here rather than
jira.

I am able to determine that the offending character is a non-breaking
space (HEX A0). We will of course remove the character from InCommon
metadata ASAP.

We have controls in place to prevent this kind of thing from happened
but it's very difficult to anticipate all possibilities. We may have
to restrict the set of permissible characters in URIs to printable
7-bit ASCII characters.

Comments or suggestions are welcome.

Tom

[1] http://md.incommon.org/InCommon/InCommon-metadata.xml


---------- Forwarded message ----------
Date: Fri, Jan 22, 2016 at 8:14 PM
Subject: [InC-Admin] bug in Incommon-metadata.xml
To: "<admin at incommon.org> Admin" <admin at incommon.org>


As reported by someone on my campus, there is a small bug in the
InCommon metadata xml.  His comment:

If I'm reading this correctly the entityID
entityID="https://passport-dev.pitt.edu/idp/shibboleth

-> json (DiscoveryFeed) has a spurious character (^Z) at the end of
the logo line (json bottom of this page.)
I'm not positive, is this caused by the space at the end of the logo
line in the InCommon Metadata.xml? Is this intentional?

It appears to break embedded discovery.

Out of context:
(InCommon-metadata.xml)

<mdui:Logo height="400" width=“400"
xml:lang="en">https://www.pitt.edu/seal/seal-400x400-72rgb.png
</mdui:Logo>

json (DiscoFeed)
"value": "https://www.pitt.edu/seal/seal-400x400-72rgb.png^Z",


Can someone take a look?