CAS Service Registry

[Walter Forbes Hoehn (wassa)]

I looked back through the shib-dev archives and found a bit of deliberation regarding how the CAS Service Registry model should be ported over to Shib, but I’m not certain if there was additional discussion offline.  Maybe this ship has sailed, but after using the PatternServiceRegistry for a while, I find myself wishing that this configuration was expressed via the SAML metadata.

The current implementation functions well and is, IMO, much more convenient to work with than the Jasig implementations.  There is an administrative overhead, however, to dealing with entities that exist outside of the scope the “standard” configuration.  A couple of examples:

1) UI templates have to be adjusted to account for multiple entity types instead of just referring to something like RpUIContext.

2) External management processes that make use of information from the metadata (<ServiceName/>, <mdui:*/>) have to take special account of the CAS entities.  Doing anything smart with audit logs, for instance, assumes an entity identifier and the ability to correlate with other metadata.

Thoughts?

-Walter