CAS OOB exception

Liam Hoekenga liamr at
Fri May 24 11:53:30 EDT 2019

On Fri, May 24, 2019 at 10:32 AM Cantor, Scott <cantor.2 at> wrote:

> On 5/24/19, 11:26 AM, "users on behalf of Liam Hoekenga" <
> users-bounces at on behalf of liamr at> wrote:
> > I tried creating metadata for it, which it wasn't pleased with.  I had
> to replace the occurrences of "&" with "&" to
> > get the IDP to load..
> & isn't legal in XML, that's just how XML works.

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

> As for the exception, I'm sure it's a bug dealing with some pathological
> empty parameter or value case.

 I'll file a bug report.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list