CAS Service Registry

[Cantor, Scott]

On 4/9/15, 3:48 PM, "Walter Forbes Hoehn (wassa)" <wassa at memphis.edu> wrote:
>
>It seems like it wouldn’t be too difficult to implement a metadata service registry alongside the existing one, but it might make for confusing discussions re: configuration.  The biggest sticking point that comes to mind is that the CAS service parameter is currently being passed to the Attribute Filter, which probably wouldn’t be what one would want if CAS clients were represented as first class entities.

Well, I think there's ancillary cleanup that just harmonizes the behavior so that whatever is exposed as the entityID is what gets passed to the components as the requester name, same as with SAML. Whether that's degenerately the service URL or indirected to something else is up to the metadata resolver to derive.

-- Scott