IDP and High Availability clarifications.

[Cantor, Scott]

On 8/10/13 11:11 AM, "Byte Flinger" <byteflinger at gmail.com> wrote:
>
>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?

It doesn't support 7 period. While we don't officially support the other
plugins, if you wanted to use the memcache plugin, you should feel free to
raise issues with it and we'll do our best. We got screwed by Terracotta,
and we're in the middle of focusing all our time on V3, so we're stuck
right now.

Paul Hethmon also has a database solution with Hibernate that he's
hopefully going to make available soon.

>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.

If you don't need any kind of real logout, I strongly urge you to consider
that, it works extremely well.

> 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?

It replaces that cookie (or can make it superfluous) but it doesn't
replace the login context cookie.

-- Scott