Can a single SP front multiple disparate applications?

[David Langenberg]

On Fri, Sep 6, 2013 at 12:50 PM, Bryan E. Wooten <bryan.wooten at utah.edu>wrote:

> Thanks for the replies.
>
> You confirmed my thoughts on this. I asked because the question came up in
> meeting today and I didn't have definitive answer. The U is considering a
> policy all IT purchased software be require to use Incommon / Shib and we
> were wondering  if this policy would extend to in house developed
> applications.
>
> While I agree with Scott philosophically about CAS (api Client
> integration) vs Shib the unfortunate reality is that CAS is much easier for
> in house developer's to implement  and results in less
> infrastructure/servers for my dept to maintain (ie many SPs).
>

I'm curious why that would be?  Over here SP care & feeding is the
responsibility of the server-group and departments not IAM.  If a dev wants
to build a shib'd app on their desktop, that's cool too, just email us the
SP metadata and about an hour later you're up & running.



>
> Another reality is that we are resource thin and asking the developers of
> these 100s of applications to move off CAS and onto Shib would take years.
>

So why not do the CAS-Shib thing and make CAS the Auth system for Shib?
 You can then move off of CAS slowly and once you're ready to go 100% shib
just replace the CAS part with shib's internal auth stuff.


Dave


-- 
David Langenberg
Identity & Access Management
The University of Chicago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130906/faa15e93/attachment-0001.html