> > I was just wondering if anybody here is familiar with both and might be > able to provide some pros/cons of consolidating CAS into the idp vs > continuing to maintain a separate CAS deployment? >
I'm very familiar with both from a development and deployment perspective. Much of the growth of Jasig CAS over the past several years has been in the area of multi-protocol support, so you'll lose anything that's not CAS or SAML; OAuth protocol support comes to mind. That's probably the biggest functional area of distinction. I would say Jasig CAS has more mature management capabilities; the service manager UI comes to mind immediately. That said, it's only a matter of time and effort before the IdP catches up in that area. There are also a lot more integration options for Jasig CAS, mostly in the area of storage backends like Ehcache and Hazelcast. Again, it's easy to develop these things for the IdP and they will probably emerge in the near future if folks need or want them. On balance, the attribute engine of the IdP is a powerful capability that has no analogue in Jasig CAS. I could probably come up with some more pros and cons to discuss, but the ones I've listed seem most notable to me as a deployer. If there are any features of interest to you in particular, please mention them and we can discuss further. Best, M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
