Andy Swiffin wrote:
>>>> On 14/08/2009 at 13:20, in message
>>>>
> <[log in to unmask]>, Jethro R Binks
> <[log in to unmask]> wrote:
>
>> I have trouble visualising the role that CAS and PubCookie play in the
>> Shibboleth world. We have used neither to this point, Shib is our first
>> excursion into any sort of Web SSO (other than contrived local schemes in
>> a couple of cases).
>>
>> That being the case, should I care about CAS/Pubcookie at this point?
>> Does it make any sense to start using them? What advantage is there to do
>> so?
>>
>> If someone has a good pointer to explain this aspect, I'd be grateful for
>> it.
>>
>
> I asked this very question back in April 2008, there are a number of replies in the archives.
>
> at the time I had intended to deploy CAS in production and even had it working quite happily with Shib. But then I couldn't work out what extra it was doing. The replies from here and elsewhere were generally of the type:
>
> We already used CAS so wanted to keep a consistent look and feel
> You can CASify more apps than you can shibbolise
> CAS gives you a customisable login form (I think the responder missed that Tomcat does too)
>
>
> In the end I decided it would do nothing for us, and that Shib provided all of the SSO that we needed. The KUSP final report Conclusions concur with this: http://www.kent.ac.uk/is/projects/kusp/documents/kusp-final-report.pdf :
>
> "7. Shibboleth SSO: Shibboleths SSO capabilities were sufficient to provide SSO without a separate package like CAS."
>
> which is why we don't use it.
>
> Andy
>
>
Same here...
Thought about it, looked at shib2, decided not to confuse things by
adding CAS when we dont use it already.
--
Jason Cormie
University of Abertay Dundee
The average nutritional value of promises is roughly zero.
The University of Abertay Dundee is a charity registered in Scotland, No: SC016040
|