IDP and High Availability clarifications.

[Byte Flinger]

Hi

I have been doing some reading on the wiki regarding High Availability for
Shibboleth IDP and the recommended solution seems to be Terracota however
having never worked with Terracota before I have a few questions:

Going on Terracota's website they seems to have layed down the open source
version of Terracota and now have 2 different products which seems to do
the same thing, BigMemory Max and BigMemory Go. It is a bit unclear to me
which one is the one to be used with Shibboleth, the (now discontinued)
open source product or any of the bigmemory ones?

Upon my researching I have stumbled upon some information which indicates
there may be issues with using Terracota with JDK 7 (Whichever one is
recommended by Shibboleth), is that true?

At the moment I am using a Jetty server for my tests however I am thinking
of setting up a jboss solution with a load balancer in front of it so I was
also wondering about the possibility of a stateless solution to make things
simpler since it seems to suit my needs (going from the info in the wiki)
with a cookie as done by the Ohio State login handler however I dont quite
understand the concept. Am I correct that basically a cookie is created
upon login which can be validated by any node, independently, with enough
information to securely say that the user is who he says he is? Does such
cookie replace the session cookie (_idp_session) usually used by Shibboleth?

Regards
Alexandre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130810/03faf750/attachment-0001.html