CAS Service Registry

[Marvin Addison]

>
> That's what I meant when I said that naming and locations in SAML are
> separate things, but I don't think that's true in CAS.
>

That's correct, identity == location in the CAS protocol.

But I would expect that in that kind of scenario, you don't get the luxury
> of just predefining specific URLs as being valid, it will likely be whole
> families of URLs that are used.


Indeed. Somewhere you've got to map URL groups/families to individual
logical services. There's no way around that.

The UI theming case Walter mentioned made it clear that a metadata facility
for CAS has some value for specific services that need explicit
registration in a metadata


> Well, the mismatch is really the overloading of identity and location.
> This is a very common thing in systems I didn't design. ;-)
>

Point taken, but man is it ever a convenient simplification that's good
enough in most cases.

In terms of endpoint validation, SAML metadata doesn't define that, the
> SAML protocol does. By which I mean, you could define a profile of metadata
> such that the Location attribute in an AssertionConsumerService element
> with a particular Binding was a regex.
>

Thanks for sketching out a concrete implementation, Scott. Can you clarify
what you mean by "define a profile of metadata"? XML schema definition?

M <dev-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150410/3e5dcffd/attachment.html