> Only joined this list the other day so apologies if this is already known,
> but as Lee states
> the real benefit of CAS is the ability to provide SSO as wide as you like
> internally.
> This link http://www.esoeproject.org/ was passed to me by my predecessor
> at
> RSC SW Brook Schofield. They have removed the need for usernames and
> PW in 60 odd internal apps.
Bear in mind that Shibboleth is an SSO system and so every SSO benefit that
can be attributed CAS can be attributed to Shib, with the addition that you
don't have to run two SSO systems, one for external access (both ways) and
one for internal access.
I know of several campuses where they protect their internal sites with
Shib.
However there are wrinkles you need to bear in mind.
- It may be easier to "CASify" an application that it is to Shiobbolize it.
I have no knowledge of these technologies so I don't know, but I would have
thought that the difficulty lay in the SSO-izinf, not in whether you target
CAS against Shib
- If a campus has an investment with CAS it makes a lot of sense to continue
using it (at least in the short term).
- There may be other integration which is easier that CAS than Shib, SPENGO
is one which immediately springs to mind.
R
|