<div dir="ltr"><div dir="ltr">On Fri, May 24, 2019 at 10:32 AM Cantor, Scott <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 5/24/19, 11:26 AM, "users on behalf of Liam Hoekenga" <<a href="mailto:users-bounces@shibboleth.net" target="_blank">users-bounces@shibboleth.net</a> on behalf of <a href="mailto:liamr@umich.edu" target="_blank">liamr@umich.edu</a>> wrote:<br>
<br>
> I tried creating metadata for it, which it wasn't pleased with. I had to replace the occurrences of "&" with "&" to<br>
> get the IDP to load..<br>
<br>
& isn't legal in XML, that's just how XML works.<br></blockquote><div><br></div><div>Does that mean that the only as long as the CAS entityID includes an ampersand, we won't be able to create metadata for this SP and will have to fall through to the service registry?</div><div>I know that ACS location can be a substring of what's being requested, but I assume that the entityID is an exact match (which would is hard since it contains and requires an illegal character).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
As for the exception, I'm sure it's a bug dealing with some pathological empty parameter or value case.<br></blockquote><div><br></div><div> I'll file a bug report.</div><div><br></div><div>Liam</div></div></div>