Shibboleth implementation.

[Michael A Grady]

On Jan 5, 2015, at 12:03 PM, Nate Klingenstein <ndk at internet2.edu> wrote:

> Rachel,
> 
>> My first question is that related to the fact that we have a server which hosts all of our client systems. As we are only doing 'single sign-on' customisation for only one specific system (via Shibboleth), I was wondering if anyone has any experience regarding installing the Shibboleth software on a server hosting many systems. We're trying to assess whether it would be better to move this single client system to it's own dedicated server for use with Shibboleth. 
> 
> It’s totally a matter of deployment preference.  You can do whatever matches up with your preferred systems management practices.
> 
> Thanks,
> Nate.
> 

As Nate indicates, there is no "one model fits all" answer to that. A number of factors might go into your decision:

 - your current load balancing/high availability/clustering model
 - your current set of supported login options, and how the login method does, or does not, correspond to your application session management model
 - how you "trigger"/initiate login now (protect everything, lazy/only as needed, dedicated login handler that initiates an app session, ...)
 - your web server software, how you manage it, etc.
 - what you consider the likelihood of having future systems/clients utilizing Shb/SAML for the service

--
Michael A. Grady
Senior IAM Consultant, Unicon, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150105/0c1cfa62/attachment.html