IdP v2 to v3 migration success story

[Marvin Addison]

>
> I'm curious, is the CAS protocol support in the idp intended to supplant a
> standalone CAS deployment, or is it more intended for people already
> running the idp and wanting to add basic CAS support without the overhead
> of standing up another piece of software?


It's intended to be a fully functional replacement for the Jasig CAS server.


> What features/functionality would you lose if migrating from CAS 3 to idp
> 3 rather than to CAS 4?
>

It's a matter of gain and loss. The most notable functional loss would be
support for protocols like OAuth and OpenID. There are also a lot more
integration components for Jasig CAS that aren't available in the IdP,
mostly in the area of storage backends (e.g. Ehcache, Hazelcast). Those are
admittedly fairly easy to develop, and it's simply a matter of time,
effort, and interest before they show up in the IdP.

There are a number of notable gains in the IdP generally that the CAS
protocol support benefits from: attribute engine, reloadable services, ease
of upgrades.

There are other differences that we could discuss, but the above are most
important in my view as a deployer. Let me know if there are any
capabilities in particular that you'd like to compare and contrast in
further detail.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150713/df30fa30/attachment.html>